|
Hello,
On Sun, 12 Nov 2000, tc lewis wrote:
>
> what issues exist with doing dns through lvs? i'm pulling my hair out
> over this one.
>
> here's a tcpdump on my real server:
>
> 08:37:41.004616 eth0 > 192.168.1.21.1024 > 192.203.230.10.domain: 9513 NS?
> . (17)
> 08:37:42.503820 eth0 B arp who-has 192.168.1.12 tell 192.168.1.2
> 08:37:42.503842 eth0 > arp reply 192.168.1.12 (0:d0:b7:65:ec:48) is-at
> 0:d0:b7:65:ec:48 (0:c0:95:e2:a8:b1)
> 08:37:42.503943 eth0 < 208.219.36.76.64049 > 64.211.224.163.domain: 2106+
> PTR? 163.224.211.64.in-addr.arpa. (45)
> 08:37:42.504012 eth0 > 64.211.224.163 > 208.219.36.76: icmp:
> 64.211.224.163 udp port domain unreachable [tos 0xc0]
ICMP error => no listener?
Before I fully understand your message (the ARP talks for
example) one question:
Is the DNS server in the real server(s) started before the VIPs
are configured (in the real servers). Look at the logs (/var/log/messages?)
whether the DNS server is listening on VIP:53. There can be a problem if
you start your network scripts (VIPs, routes, etc) in rc.local while the
DNS server was started long before from the rc.d levels. If you
use "bind" I assume there is no listener(s) for the VIPs you add after
starting the server.
For the telnet service there is no problem. It just listens for
0.0.0.0 and when you add new VIP later it just works.
> -tcl.
Regards
--
Julian Anastasov <ja@xxxxxx>
|
