[nzlug] Bind question:

[Mark Goldfinch]

Chris Hodgetts wrote:
> They return the same serial number....
>
> when you dig @ns1.example.com example.com you get the correct
> information from the zone file:
>
> caitlin:/etc/bind/primary# dig @ns1.example.com example.com
>
> ; <<>> DiG 9.4.2 <<>> @master.example.com example.com
> ; (1 server found)
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49577
> ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
> ;; WARNING: recursion requested but not available
>
> ;; QUESTION SECTION:
> ;example.com.			IN	A
>
> ;; ANSWER SECTION:
> example.com.		86400	IN	A	XXX.XXX.XXX.XXX
>
> ;; Query time: 512 msec
> ;; SERVER: XXX.XXX.XXX.XXX#53(XXX.XXX.XXX.XXX)
> ;; WHEN: Fri Jun  6 14:23:12 2008
> ;; MSG SIZE  rcvd: 54
>
> And the A records are different, but the SOA / Serial Numbers are
> identical.
>
> When you query internally on the same network to ns1.example.com you get
> the correct results, its just when you try and query it externally...
>
> Any help comments, suggestions, remarks, that might help would be
> appreciated.
>   

Did someone update the A record and forget to bump the serial number?  
Try updating the serial number and reloading the zone on your master 
bind instance and see whether everyone else gets the updated A record as 
you'd expect..

Did you have a look at the logs on your slave servers to see whether 
they think there's something wrong?  Otherwise are your slave servers 
able to perform AXFR transfers off your master?

Some ideas to start with anyway..

Thanks,
Mark.