Strange Incorrect DNS Query Results

Cloaked Hunter djholt at
Tue Dec 7 20:00:12 UTC 2004

I am experiencing a very strange problem with my DNS setup and I was
hoping someone could provide some assistance. Any help would be greatly

With a partner, I have set up two DNS servers. Each server is acting a
primary DNS server as well as a secondary DNS server for the other
server. Here is a summary of my setup:

DNS Server #1:
Address: (,
Master Domains:,,
Slave Domains:

DNS Server #2:
Address: (,
Master Domains:
Slave Domains:,,

Both of my DNS servers return correct results for all of my master and
slave hostnames if asked directly. The problem, however, occurs when I
attempt to perform a lookup using a select number of other DNS servers.
When queried for one of my hostnames, rather than providing the correct
IP address, these select DNS servers will always return the IP address
of my secondary DNS server with a zero TTL. When queried immediately
after, they then return the correct IP address with the correct TTL
(3600 seconds). After that TTL expires they again return the incorrect
IP address and zero TTL. I have upgraded both of my DNS servers from
BIND 9.2.3 to 9.3.0, and it did not affect anything. Most DNS servers I
have tested work fine and always return correct results when queried.
Regardless, I must get this problem resolved as my ISP's DNS server
happens to be one of the DNS servers returning the incorrect results.
The following are the only DNS servers I have found which return the
incorrect results:

Random Charter DNS Servers: ( ( ( (

My ISP's DNS Servers
(These servers may not accept outside queries) ( (

; <<>> DiG 9.2.1 <<>> @
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18516
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 12

;       IN      A

;; ANSWER SECTION: 0      IN      A

com.                    169092  IN      NS      G.GTLD-SERVERS.NET.
com.                    169092  IN      NS      H.GTLD-SERVERS.NET.
com.                    169092  IN      NS      I.GTLD-SERVERS.NET.
com.                    169092  IN      NS      J.GTLD-SERVERS.NET.
com.                    169092  IN      NS      K.GTLD-SERVERS.NET.
com.                    169092  IN      NS      L.GTLD-SERVERS.NET.
com.                    169092  IN      NS      M.GTLD-SERVERS.NET.
com.                    169092  IN      NS      A.GTLD-SERVERS.NET.
com.                    169092  IN      NS      B.GTLD-SERVERS.NET.
com.                    169092  IN      NS      C.GTLD-SERVERS.NET.
com.                    169092  IN      NS      D.GTLD-SERVERS.NET.
com.                    169092  IN      NS      E.GTLD-SERVERS.NET.
com.                    169092  IN      NS      F.GTLD-SERVERS.NET.

A.GTLD-SERVERS.NET.     115223  IN      A
A.GTLD-SERVERS.NET.     74250   IN      AAAA    2001:503:a83e::2:30
B.GTLD-SERVERS.NET.     14836   IN      A
B.GTLD-SERVERS.NET.     34331   IN      AAAA    2001:503:231d::2:30
C.GTLD-SERVERS.NET.     168884  IN      A
D.GTLD-SERVERS.NET.     13068   IN      A
E.GTLD-SERVERS.NET.     99607   IN      A
F.GTLD-SERVERS.NET.     90885   IN      A
G.GTLD-SERVERS.NET.     171000  IN      A
H.GTLD-SERVERS.NET.     90885   IN      A
I.GTLD-SERVERS.NET.     91875   IN      A
J.GTLD-SERVERS.NET.     97650   IN      A

;; Query time: 144 msec
;; WHEN: Tue Dec  7 12:01:02 2004
;; MSG SIZE  rcvd: 497

; <<>> DiG 9.2.1 <<>> @
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52266
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;       IN      A

;; ANSWER SECTION: 3600   IN      A

;; AUTHORITY SECTION: 3600   IN      NS 3600   IN      NS

;; Query time: 134 msec
;; WHEN: Tue Dec  7 12:01:28 2004
;; MSG SIZE  rcvd: 93

More information about the bind-users mailing list