SQUISH LOGO  
 


  << Previous Topic | Next Topic >>Return to Index  

UDP DNS requests are failing

January 15 2008 at 5:00 AM
  (Login hgunasin)

Hi,

I have a very specific issue with resolving auppa01.sydney.bhdc.mebs.ihost.com Name to IP using DNS Servers @ wehid.wehi.edu.au.

However, If I use dig with forced TCP, it resolves fine. Also, from many other DNSs, I could resolve without any issues with UDP and TCP both.

Any hints why this specific DNS cant resolve using UDP for above name to IP using the DNS given?. Dig outputs are given below;

Working DIG:
# dig @129.33.32.102 auppa01.sydney.bhdc.mebs.ihost.com +tcp

; <<>> DiG 9.2.4 <<>> @129.33.32.102 auppa01.sydney.bhdc.mebs.ihost.com +tcp
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16048
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;auppa01.sydney.bhdc.mebs.ihost.com. IN A

;; AUTHORITY SECTION:
bhdc.mebs.ihost.com. 3600 IN NS
aubhqdn02ict5x2.noc04.mebs.ihost.com.
bhdc.mebs.ihost.com. 3600 IN NS
aubhqdn01ict5x2.noc04.mebs.ihost.com.

;; ADDITIONAL SECTION:
aubhqdn01ict5x2.noc04.mebs.ihost.com. 3600 IN A 203.184.65.132
aubhqdn02ict5x2.noc04.mebs.ihost.com. 3600 IN A 203.184.65.133

;; Query time: 252 msec
;; SERVER: 129.33.32.102#53(129.33.32.102)
;; WHEN: Fri Jan 11 11:19:34 2008
;; MSG SIZE rcvd: 150


NON Working DIG:

dig +trace auppa01.sydney.bhdc.mebs.ihost.com

; <<>> DiG 9.2.4 <<>> +trace auppa01.sydney.bhdc.mebs.ihost.com
;; global options: printcmd
. 3600000 IN NS E.ROOT-SERVERS.NET.
. 3600000 IN NS F.ROOT-SERVERS.NET.
. 3600000 IN NS G.ROOT-SERVERS.NET.
. 3600000 IN NS H.ROOT-SERVERS.NET.
. 3600000 IN NS I.ROOT-SERVERS.NET.
. 3600000 IN NS J.ROOT-SERVERS.NET.
. 3600000 IN NS K.ROOT-SERVERS.NET.
. 3600000 IN NS L.ROOT-SERVERS.NET.
. 3600000 IN NS M.ROOT-SERVERS.NET.
. 3600000 IN NS A.ROOT-SERVERS.NET.
. 3600000 IN NS B.ROOT-SERVERS.NET.
. 3600000 IN NS C.ROOT-SERVERS.NET.
. 3600000 IN NS D.ROOT-SERVERS.NET.
;; Received 420 bytes from 128.250.252.74#53(128.250.252.74) in 1 ms

com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
com. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
com. 172800 IN NS B.GTLD-SERVERS.NET.
;; Received 508 bytes from 192.203.230.10#53(E.ROOT-SERVERS.NET) in 170 ms

ihost.com. 172800 IN NS ns.almaden.ibm.com.
ihost.com. 172800 IN NS ns.austin.ibm.com.
ihost.com. 172800 IN NS ns.watson.ibm.com.
;; Received 177 bytes from 192.42.93.30#53(G.GTLD-SERVERS.NET) in 171 ms

mebs.ihost.com. 86400 IN NS rtpussdnsb02.mebs.ihost.com.
mebs.ihost.com. 86400 IN NS rtpussdnsb01.mebs.ihost.com.
;; Received 138 bytes from 198.4.83.35#53(ns.almaden.ibm.com) in 200 ms

dig: couldn't get address for 'rtpussdnsb02.mebs.ihost.com': failure


 

 Respond to this message   
Current Topic - UDP DNS requests are failing
  << Previous Topic | Next Topic >>Return to Index  
 Copyright © 1999-2009 Network54. All rights reserved.   Terms of Use   Privacy Statement  
james at squish dot net