Project

General

Profile

Actions

Bug #1699

closed

nfdc create: Host not found (authoritative)

Added by Junxiao Shi over 11 years ago. Updated over 11 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Faces
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Environment: A-D

Steps to reproduce:

  1. on host A, start bind9 on host with this zone file:

    $ORIGIN .
    $TTL    20
    autoconfig-test.tmp._homehub._autoconf.named-data.net    IN    SOA    ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net. root.autoconfig-test.tmp._homehub._autoconf.named-data.net. (
                      3        ; Serial
                 604800        ; Refresh
                  86400        ; Retry
                2419200        ; Expire
                 604800 )    ; Negative Cache TTL
    ;
    autoconfig-test.tmp._homehub._autoconf.named-data.net.        IN    NS    ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net.
    autoconfig-test.tmp._homehub._autoconf.named-data.net.           IN      MX    10      ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net.
    
    _ndn._udp.autoconfig-test.tmp._homehub._autoconf.named-data.net.    SRV    0    0    6363    ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net.
    $ORIGIN autoconfig-test.tmp._homehub._autoconf.named-data.net.
    
    localhost     A     127.0.0.1
    ns1           A   10.63.18.3
    
  2. on host D, write the following to /etc/resolv.conf

    search autoconf-test-none.named-data.net
    nameserver <hostA's IP>
    
  3. on host D, execute nfdc create udp://ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net:6363

Expected: face udp4://10.63.18.3:6363 is created

Actual: ERROR: Face creation failed: Remote endpoint hostname or port cannot be resolved: Host not found (authoritative) (code: 408)

Note: This bug is discovered during ndn-autoconfig testing, but it's unrelated to autoconfig.

Note: 10.63.18.3 is an unreachable IP address in the environment, but UDP face doesn't depend on destination IP being reachable.


Files

1.pcap (2.07 KB) 1.pcap tcpdump on host D during nfdc create Junxiao Shi, 06/26/2014 02:00 AM
Actions #1

Updated by Alex Afanasyev over 11 years ago

Can you show output of

dig ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net
Actions #2

Updated by Junxiao Shi over 11 years ago

integ@d:~$ nfdc create udp://ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net:6363
1403832851.859909 INFO: [FaceTable] Added face id=7 remote=fd://24 local=unix:///run/nfd.sock
ERROR: Face creation failed: Remote endpoint hostname or port cannot be resolved: Host not found (authoritative) (code: 408)
1403832851.886629 INFO: [UnixStreamFace] [id:7,endpoint:/run/nfd.sock] Connection closed
integ@d:~$ 1403832851.895263 INFO: [FaceTable] Removed face id=7 remote=fd://24 local=unix:///run/nfd.sock

integ@d:~$ dig ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net

; <<>> DiG 9.8.1-P1 <<>> ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4379
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net. IN A

;; ANSWER SECTION:
ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net. 20 IN A 10.63.18.3

;; AUTHORITY SECTION:
autoconfig-test.tmp._homehub._autoconf.named-data.net. 20 IN NS ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net.

;; Query time: 11 msec
;; SERVER: 10.1.0.1#53(10.1.0.1)
;; WHEN: Thu Jun 26 19:34:20 2014
;; MSG SIZE  rcvd: 105

integ@d:~$ nslookup -q=aaaa ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net
Server:     10.1.0.1
Address:    10.1.0.1#53

*** Can't find ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net: No answer

integ@d:~$ nslookup -q=a ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net
Server:     10.1.0.1
Address:    10.1.0.1#53

Name:   ns1.autoconfig-test.tmp._homehub._autoconf.named-data.net
Address: 10.63.18.3
Actions #3

Updated by Alex Afanasyev over 11 years ago

Do not confirm this issue on OSX 10.9, though with slightly different zone (but it shouldn't matter):

zone "test" in named.conf

[cawka@cawka-mac local (master)]$ cat var/named/test
@    IN    SOA    ns1 root (
                  3        ; Serial
             604800        ; Refresh
              86400        ; Retry
            2419200        ; Expire
             604800 )    ; Negative Cache TTL
;

@        IN    NS      ns1
@        IN      MX    10      ns1

_ndn._udp    SRV    0    0    6363    ns1

localhost     A   127.0.0.1
ns1           A   10.63.18.3


[cawka@cawka-mac ~]$ dig +short ns1.test a
10.63.18.3


[cawka@cawka-mac ~]$ nfdc create udp://ns1.test
Face creation succeeded: ControlParameters(FaceId: 10, Uri: udp4://10.63.18.3:6363, )
Actions #4

Updated by Junxiao Shi over 11 years ago

Please test with the given zone name.
Hila believes the underscore in zone name matters.

Actions #5

Updated by Alex Afanasyev over 11 years ago

I tried to reproduce the problem with bind in 14.04, but it always refused to load this zone.

I've added test record to real _homehub._autoconf.named-data.net. zone:

[cawka@cawka-mac ~]$ dig test._homehub._autoconf.named-data.net

; <<>> DiG 9.8.3-P1 <<>> test._homehub._autoconf.named-data.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5388
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 0

;; QUESTION SECTION:
;test._homehub._autoconf.named-data.net.    IN A

;; ANSWER SECTION:
test._homehub._autoconf.named-data.net. 86400 IN A 1.1.1.1

;; AUTHORITY SECTION:
_autoconf.named-data.net. 86400 IN  NS  flea.netsec.colostate.edu.
_autoconf.named-data.net. 86400 IN  NS  sec64.netsec.colostate.edu.
_autoconf.named-data.net. 86400 IN  NS  zinc.cs.ucla.edu.

;; Query time: 1 msec
;; SERVER: 131.179.196.160#53(131.179.196.160)
;; WHEN: Fri Jun 27 15:17:00 2014
;; MSG SIZE  rcvd: 158

On OSX 10.9, I don't see the problem

[cawka@cawka-mac ~]$ nfdc create udp://test._homehub._autoconf.named-data.net
Face creation succeeded: ControlParameters(FaceId: 9, Uri: udp4://1.1.1.1:6363, )
Actions #6

Updated by Alex Afanasyev over 11 years ago

Ok. Finally was able to reproduce the problem, on Ubuntu 14.04

Actions #7

Updated by Junxiao Shi over 11 years ago

I'd like to reject this Bug because a hostname that contains underscore violates RFC 952, which says:

 1. A "name" (Net, Host, Gateway, or Domain name) is a text string up
 to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus
 sign (-), and period (.).
Actions #8

Updated by Alex Afanasyev over 11 years ago

I agree to reject this. This is not NFD or even boost asio problem. This has something to do with Ubuntu's getaddrinfo. If you try to

nc test._homehub._autoconf.named-data.net. 1

or even ping this host, it should fail on Ubuntu.

I found a couple of topic on google about then, none of them helped to solve the problem, but they all suggest that it is something to do with the underscore that is suppose to be used only in mDNS.

Actions #9

Updated by Junxiao Shi over 11 years ago

  • Status changed from New to Rejected

Rejected based on reason in note-7 and note-8.

Actions

Also available in: Atom PDF