[Rocks-Discuss] FE not resolving DNS on public interface

Charles Kovalsky CKovalsky at awstruepower.com
Fri Jun 7 07:38:57 PDT 2013


Hello all,

I am having a small issue with DNS on the frontend.  I am unable to resolve any DNS names on my public network.  I am able to ping/ssh/everything else via IP address, so I don't think it is a routing issue but I could be wrong.  Anyone have any clues as to what I should look at first to try and resolve this?  Named is running and I can resolve dns on the private network just fine.

Below are the outputs of some commands in case they help.

Regards,

Chuck.

[root at awsrocks ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
TYPE=Bridge
IPADDR=172.20.11.105
NETMASK=255.255.255.0
BOOTPROTO=none
ONBOOT=yes
MTU=1500

[root at awsrocks ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2
TYPE=Bridge
IPADDR=10.105.0.1
NETMASK=255.255.0.0
BOOTPROTO=none
ONBOOT=yes
MTU=1500

[root at awsrocks named]# /sbin/route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
255.255.255.255 0.0.0.0         255.255.255.255 UH    0      0        0 eth2
172.20.11.105   10.105.0.1      255.255.255.255 UGH   0      0        0 eth2
172.20.11.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0
224.0.0.0       0.0.0.0         255.255.255.0   U     0      0        0 eth2
10.105.0.0      0.0.0.0         255.255.0.0     U     0      0        0 eth2
169.254.0.0     0.0.0.0         255.255.0.0     U     1006   0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1007   0        0 eth2
0.0.0.0         172.20.11.1     0.0.0.0         UG    0      0        0 eth0

[root at awsrocks named]# rocks list network
NETWORK  SUBNET      NETMASK       MTU   DNSZONE           SERVEDNS
private: 10.105.0.0  255.255.0.0   1500  local             True
public:  172.20.11.0 255.255.255.0 1500  awstruewind.local False

[root at awsrocks named]# ping awsdc3
ping: unknown host awsdc3

[root at awsrocks named]# traceroute awsdc3
awsdc3: Name or service not known
Cannot handle "host" cmdline arg `awsdc3' on position 1 (argc 1)

[root at awsrocks named]# ping 172.20.1.61
PING 172.20.1.61 (172.20.1.61) 56(84) bytes of data.
64 bytes from 172.20.1.61: icmp_seq=1 ttl=127 time=0.332 ms
64 bytes from 172.20.1.61: icmp_seq=2 ttl=127 time=0.303 ms
64 bytes from 172.20.1.61: icmp_seq=3 ttl=127 time=0.224 ms

[root at awsrocks named]# traceroute 172.20.1.61
traceroute to 172.20.1.61 (172.20.1.61), 30 hops max, 60 byte packets
1  172.20.11.1 (172.20.11.1)  0.311 ms  0.315 ms  0.364 ms
2  awsdc3.awstruewind.local (172.20.1.61)  0.192 ms * *

[root at awsrocks named]# cat /etc/resolv.conf
search local awstruewind.local
nameserver 127.0.0.1
nameserver 172.20.1.61
nameserver 172.20.1.63


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20130607/1e1efb9c/attachment.html 


More information about the npaci-rocks-discussion mailing list