[CentOS] Centos 5.4 DNS resolution issue

[Gaurav N.]

Here's the dig-google.pcap file attached, if it helps.

Best Regards,
Gaurav


On Tue, Mar 9, 2010 at 1:25 AM, Gaurav N. <gaurav.knangla at gmail.com> wrote:

> UPDATE:
>
> I tried with FreeBSD8 as well and the DNS query didn't work. This is
> beginning to look more and more like an issue with my UTStarcom *WA3002G4
> ADSL2+ Router and its NAT config or the lack of it.*
> *
> *
> *My setup and the ip addresses:*
> *Router         192.168.1.1*
> *Windows      192.168.1.2*
> *Centos 5.4   192.168.1.3*
> *FreeBSD8    192.168.1.4*
> *
> *
> *The windows host works fine with no issues with DNS queries.*
>
> Best Regards,
> Gaurav
>
>
>
>
> On Tue, Mar 9, 2010 at 12:08 AM, Gaurav Nangla <gaurav.knangla at gmail.com>wrote:
>
>> [root at cent5 ~]# dig www.google.com @208.67.220.220
>>
>> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5 <<>> www.google.com @
>> 208.67.220.220
>>  ;; global options:  printcmd
>> ;; connection timed out; no servers could be reached
>>
>> Best Regards,
>> Gaurav
>>
>>
>>
>> On Mon, Mar 8, 2010 at 5:21 PM, Pitshou Asingalembi <depitsho at yahoo.fr>wrote:
>>
>>> John R Pierce wrote:
>>> > Gaurav Nangla wrote:
>>> >
>>> >> I can ping the google.com <http://google.com> ip addresses
>>> >> (209.85.231.104) but can't ping the FQDN, obviously DNS is broken.
>>> >>
>>> >> I can also ping the nameserver ip addresses specified in
>>> /etc/resolv.conf.
>>> >>
>>> >
>>> > well, the DNS servers given by your resolv.conf output seem valid from
>>> > here..  I recommend doing some more debugging with `host` or similar
>>> DNS
>>> > diagnostic tools.
>>> >
>>> > note regular DNS lookups like these tend to use UDP rather than TCP, if
>>> > you're behind a NAT firewall which doesn't allow outbound udp port 53
>>> > and connection track the response, then things might not work well.
>>> >
>>> >
>>> > $ host google.com 208.67.220.220
>>> > Using domain server:
>>> > Name: 208.67.220.220
>>> > Address: 208.67.220.220#53
>>> > Aliases:
>>> >
>>> > google.com has address 74.125.19.105
>>> > google.com has address 74.125.19.99
>>> > google.com has address 74.125.19.103
>>> > google.com has address 74.125.19.106
>>> > google.com has address 74.125.19.147
>>> > google.com has address 74.125.19.104
>>> > google.com mail is handled by 400 google.com.s9b2.psmtp.com.
>>> > google.com mail is handled by 200 google.com.s9a2.psmtp.com.
>>> > google.com mail is handled by 300 google.com.s9b1.psmtp.com.
>>> > google.com mail is handled by 100 google.com.s9a1.psmtp.com.
>>> >
>>> > $ host google.com 208.67.222.222
>>> > Using domain server:
>>> > Name: 208.67.222.222
>>> > Address: 208.67.222.222#53
>>> > Aliases:
>>> >
>>> > google.com has address 74.125.19.105
>>> > google.com has address 74.125.19.147
>>> > google.com has address 74.125.19.99
>>> > google.com has address 74.125.19.103
>>> > google.com has address 74.125.19.104
>>> > google.com has address 74.125.19.106
>>> > google.com mail is handled by 400 google.com.s9b2.psmtp.com.
>>> > google.com mail is handled by 200 google.com.s9a2.psmtp.com.
>>> > google.com mail is handled by 300 google.com.s9b1.psmtp.com.
>>> > google.com mail is handled by 100 google.com.s9a1.psmtp.com.
>>> > _______________________________________________
>>> > CentOS mailing list
>>> > CentOS at centos.org
>>> > http://lists.centos.org/mailman/listinfo/centos
>>> >
>>> >
>>> please try:
>>> dig www.google.com @IPofyourDNSserver
>>> and send me the output
>>> _______________________________________________
>>> CentOS mailing list
>>> CentOS at centos.org
>>> http://lists.centos.org/mailman/listinfo/centos
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos/attachments/20100309/61c97cb8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dig-google.pcap
Type: application/octet-stream
Size: 9267 bytes
Desc: not available
URL: <http://lists.centos.org/pipermail/centos/attachments/20100309/61c97cb8/attachment.obj>