This is a discussion on Strange Incorrect DNS Query Results within the Bind Users forums, part of the DNS and Related Forums category; I am experiencing a very strange problem with my DNS setup and I was hoping someone could provide some assistance. ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
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 appreciated! 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: 209.33.199.95 (ns1.cloakedhunter.com, ns2.doctor9.net) Master Domains: cloakedhunter.com, justpicturethisinc.com, 3hlandscapeproducts.com Slave Domains: doctor9.net DNS Server #2: Address: 67.42.122.123 (ns2.cloakedhunter.com, ns1.doctor9.net) Master Domains: doctor9.net Slave Domains: cloakedhunter.com, justpicturethisinc.com, 3hlandscapeproducts.com 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: 24.213.60.77 (ns1.chartermi.net) 24.213.60.78 (ns2.chartermi.net) 24.247.24.38 (ns3.chartermi.net) 24.213.28.38 (ns4.chartermi.net) My ISP's DNS Servers (These servers may not accept outside queries) 204.17.177.10 (ns1.infowest.com) 204.17.177.20 (ns2.infowest.com) -------------------------------------------------- ---EXAMPLE OF INCORRECT DNS QUERY USING DIG:--- -------------------------------------------------- ; <<>> DiG 9.2.1 <<>> @204.17.177.20 3hlandscapeproducts.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18516 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 12 ;; QUESTION SECTION: ;3hlandscapeproducts.com. IN A ;; ANSWER SECTION: 3hlandscapeproducts.com. 0 IN A 67.42.122.123 ;; AUTHORITY SECTION: 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. ;; ADDITIONAL SECTION: A.GTLD-SERVERS.NET. 115223 IN A 192.5.6.30 A.GTLD-SERVERS.NET. 74250 IN AAAA 2001:503:a83e::2:30 B.GTLD-SERVERS.NET. 14836 IN A 192.33.14.30 B.GTLD-SERVERS.NET. 34331 IN AAAA 2001:503:231d::2:30 C.GTLD-SERVERS.NET. 168884 IN A 192.26.92.30 D.GTLD-SERVERS.NET. 13068 IN A 192.31.80.30 E.GTLD-SERVERS.NET. 99607 IN A 192.12.94.30 F.GTLD-SERVERS.NET. 90885 IN A 192.35.51.30 G.GTLD-SERVERS.NET. 171000 IN A 192.42.93.30 H.GTLD-SERVERS.NET. 90885 IN A 192.54.112.30 I.GTLD-SERVERS.NET. 91875 IN A 192.43.172.30 J.GTLD-SERVERS.NET. 97650 IN A 192.48.79.30 ;; Query time: 144 msec ;; SERVER: 204.17.177.20#53(204.17.177.20) ;; WHEN: Tue Dec 7 12:01:02 2004 ;; MSG SIZE rcvd: 497 -------------------------------------------------- ---EXAMPLE OF CORRECT DNS QUERY USING DIG:--- -------------------------------------------------- ; <<>> DiG 9.2.1 <<>> @204.17.177.20 3hlandscapeproducts.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52266 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;3hlandscapeproducts.com. IN A ;; ANSWER SECTION: 3hlandscapeproducts.com. 3600 IN A 209.33.199.95 ;; AUTHORITY SECTION: 3hlandscapeproducts.com. 3600 IN NS ns1.3hlandscapeproducts.com. 3hlandscapeproducts.com. 3600 IN NS ns2.3hlandscapeproducts.com. ;; Query time: 134 msec ;; SERVER: 204.17.177.20#53(204.17.177.20) ;; WHEN: Tue Dec 7 12:01:28 2004 ;; MSG SIZE rcvd: 93 |
![]() |
| Thread Tools | |
| Display Modes | |
|
|