reply from unexpected source?

[Kitchens, Douglas]

Adam Olsen writes:
	Here is my attempted zone file for thedaily8.com:
$TTL    604800
@           IN      SOA ns1.thedaily8.com. root.thedaily8.com. (
           20080538     ; Serial
             604800     ; Refresh
              86400     ; Retry
            2419200     ; Expire
             604800 )   ; Negative Cache TTL
;

@       IN  NS  ns1
        IN  A   206.71.90.6
www     IN  A   206.71.90.6
ns1     IN  A   206.71.90.7

When querying the server for thedaily8.com like this:

dig thedaily8.com @206.71.90.6, I get the following:

;; reply from unexpected source: 206.71.90.5#53, expected 206.71.90.7#53
;; reply from unexpected source: 206.71.90.5#53, expected 206.71.90.7#53

What am I doing wrong here?


Adam, 
	I have seen a similar issue when running a cluster behind a load
balancer. The query is sent to the VIP, but to avoid pounding our load
balancer, our individual servers were set up to bypass the load balancer
on the reply. Thus, queries sent to the VIP were replying from a
different IP. To get around this issue, we set up a loopback on the
servers with the VIP IP, then routed the reply's through this. 

Ex:

# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:14:4F:46:1E:3E  
          inet addr:208.180.83.145  Bcast:208.180.83.159
Mask:255.255.255.224
          inet6 addr: fe80::214:4fff:fe46:1e3e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1413155005 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1844524594 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:956379931 (912.0 MiB)  TX bytes:3987346638 (3.7 GiB)
          Base address:0x9c00 Memory:fbfe0000-fc000000 

eth1      Link encap:Ethernet  HWaddr 00:14:4F:46:1E:3F  
          inet addr:208.180.83.175  Bcast:208.180.83.191
Mask:255.255.255.224
          inet6 addr: fe80::214:4fff:fe46:1e3f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:476622524 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5817931 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2316880170 (2.1 GiB)  TX bytes:430652903 (410.7 MiB)
          Base address:0x9800 Memory:fbfc0000-fbfe0000 
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:421968331 errors:0 dropped:0 overruns:0 frame:0
          TX packets:421968331 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3406071449 (3.1 GiB)  TX bytes:3406071449 (3.1 GiB)
lo:1      Link encap:Local Loopback  
          inet addr:208.180.83.133  Mask:0.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1

lo:2      Link encap:Local Loopback  
          inet addr:208.180.83.165  Mask:0.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
Behalf Of Adam Olsen
Sent: Monday, July 28, 2008 12:31 PM
To: bind-users
Subject: reply from unexpected source?

Here is my attempted zone file for thedaily8.com:
$TTL    604800
@           IN      SOA ns1.thedaily8.com. root.thedaily8.com. (
           20080538     ; Serial
             604800     ; Refresh
              86400     ; Retry
            2419200     ; Expire
             604800 )   ; Negative Cache TTL
;

@       IN  NS  ns1
        IN  A   206.71.90.6
www     IN  A   206.71.90.6
ns1     IN  A   206.71.90.7

When querying the server for thedaily8.com like this:

dig thedaily8.com @206.71.90.6, I get the following:

;; reply from unexpected source: 206.71.90.5#53, expected 206.71.90.7#53
;; reply from unexpected source: 206.71.90.5#53, expected 206.71.90.7#53

What am I doing wrong here?

-- 
Adam Olsen
SendOutCards.com
http://www.vimtips.org
http://last.fm/user/synic