Opened 7 years ago

Closed 7 years ago

#32 closed (fixed)

DNS entries are not defined for 8052.bbn.xo and 8264.bbn.xo

Reported by: chaos@bbn.com Owned by: jonmills@renci.org
Priority: major Milestone: EG-ADM-1
Component: Administration Version: SPIRAL4
Keywords: Cc:
Dependencies:

Description

From a login on bbn-hn, i see:

bbn-hn,[~],13:39(0)$ nslookup
> server
Default server: 152.54.1.66
Address: 152.54.1.66#53
Default server: 192.1.249.10
Address: 192.1.249.10#53
> 8052.bbn.xo
Server:         152.54.1.66
Address:        152.54.1.66#53

** server can't find 8052.bbn.xo: NXDOMAIN
> 8064.bbn.xo
Server:         152.54.1.66
Address:        152.54.1.66#53

** server can't find 8064.bbn.xo: NXDOMAIN
> 192.168.103.2
Server:         152.54.1.66
Address:        152.54.1.66#53

** server can't find 2.103.168.192.in-addr.arpa.: NXDOMAIN
> 192.168.103.4
Server:         152.54.1.66
Address:        152.54.1.66#53

** server can't find 4.103.168.192.in-addr.arpa.: NXDOMAIN
> 

Based on Wednesday's call, i believe the DNS server at 152.54.1.66 should be serving records for things in bbn.xo (vlan 1006), so i think this is a bug.

Change History (11)

comment:1 Changed 7 years ago by chaos@bbn.com

Ping. This is still blocking EG-ADM-1.

comment:2 Changed 7 years ago by vjo@duke.edu

Owner: changed from somebody to vjo@duke.edu

comment:3 Changed 7 years ago by chaos@bbn.com

Summary: DNS entries are not defined for 8052.bbn.xo and 8064.bbn.xoDNS entries are not defined for 8052.bbn.xo and 8264.bbn.xo

Reminder: this ticket (debugging DNS entries for 8052.bbn.xo and 8264.bbn.xo so they can be looked up from bbn-hn itself) still blocks EG-ADM-1.

comment:4 Changed 7 years ago by chaos@bbn.com

Resolution: fixed
Status: newclosed

Looks like Victor fixed this. From bbn-hn:

bbn-hn,[~],19:43(0)$ host bbn-8052.bbn.xo
bbn-8052.bbn.xo has address 192.168.103.2
bbn-hn,[~],19:45(0)$ host bbn-8052
bbn-8052.bbn.xo has address 192.168.103.2
bbn-hn,[~],19:45(0)$ host bbn-8264.bbn.xo
bbn-8264.bbn.xo has address 192.168.103.4
bbn-hn,[~],19:45(0)$ host bbn-8264
bbn-8264.bbn.xo has address 192.168.103.4

and the hostnames of the switches match:

bbn-hn,[~],19:45(0)$ ssh bbn-8052
Enter radius password: 
...
bbn-8052.bbn.xo>

bbn-hn,[~],19:46(130)$ ssh bbn-8264
Enter radius password: 
...
bbn-8264.bbn.xo>

Looks good. Thanks.

comment:5 Changed 7 years ago by chaos@bbn.com

Resolution: fixed
Status: closedreopened

This has become un-fixed:

bbn-hn,[~],18:39(255)$ host bbn-8052.bbn.xo
Host bbn-8052.bbn.xo not found: 3(NXDOMAIN)
bbn-hn,[~],18:39(1)$ host bbn-8264.bbn.xo
Host bbn-8264.bbn.xo not found: 3(NXDOMAIN)

comment:6 Changed 7 years ago by chaos@bbn.com

Ping. Does anyone know why these lookups stopped working?

comment:7 Changed 7 years ago by ibaldin@renci.org

8264.bbn.xo works at least via VPN.

comment:8 Changed 7 years ago by chaos@bbn.com

Ilia: two things:

  1. It may work via VPN, but it does not work on bbn-hn:
    bbn-hn,[~],18:34(0)$ host 8264
    Host 8264 not found: 3(NXDOMAIN)
    
    bbn-hn,[~],18:34(1)$ host 8264.bbn.xo
    Host 8264.bbn.xo not found: 3(NXDOMAIN)
    
  2. We agreed after some discussion (see 4) that the hostnames should be bbn-8264 and bbn-8052, not 8264 and 8052. (To be absolutely clear, these names do not work from bbn-hn either.) Mind you, i don't care what the hostnames are, but:
    • The DNS names should match what the devices believe their own hostnames to be, which is currently bbn-8052.bbn.xo and bbn-8264.bbn.xo
    • The DNS names should not change arbitrarily often.

comment:9 Changed 7 years ago by chaos@bbn.com

Owner: changed from vjo@duke.edu to jonmills@renci.org
Status: reopenednew

Ah, never mind: Jonathan claims via e-mail that this problem is related to work he is doing with makedns. So it is a known outage.

comment:10 Changed 7 years ago by lnevers@bbn.com

This is the status as of 10/10/2012 for DNS:

[lnevers@bbn-hn ~]$  host bbn-8052.bbn.xo
bbn-8052.bbn.xo has address 192.168.103.2
[lnevers@bbn-hn ~]$ host bbn-8052
bbn-8052.exogeni.net is an alias for bbn-8052.exogeni.gpolab.bbn.com.
bbn-8052.exogeni.gpolab.bbn.com has address 192.1.242.4
[lnevers@bbn-hn ~]$ host bbn-8264.bbn.xo
bbn-8264.bbn.xo has address 192.168.103.4
[lnevers@bbn-hn ~]$ host bbn-8264
bbn-8264.bbn.xo has address 192.168.103.4

And the access to the switches:

[lnevers@bbn-hn ~]$ ssh bbn-8052
...
bbn-8052.bbn.xo>


[lnevers@bbn-hn ~]$ ssh bbn-8264
...
bbn-8264.bbn.xo>

Is this ticket addressed?

comment:11 Changed 7 years ago by chaos@bbn.com

Resolution: fixed
Status: newclosed

Agreed, it looks like this is now working again.

Note: See TracTickets for help on using tickets.