[SOLVED] Hints not working on Kresd

Software SW bugs discussion
1

Hi,
It seems kresd doesn’t resolve the hints.
My kresd.config is self generated.
Hints are there, but they don’t resolve.

Any idea on what the problem is?

 root@turris:~# cat /tmp/kresd.config
    --Automatically generated file; DO NOT EDIT
    modules = {
        'hints'
      , 'policy'
      , 'stats'
      , predict = {
            window = 30 -- 30 minutes sampling window
          , period = 24*(60/30) -- track last 24 hours
      }
    }
    hints.config('/etc/hosts')
    hints['Unknown.lan'] = '192.168.1.144'
    hints['Foscam.lan'] = '192.168.1.98'
    hints['Ecobee3.lan'] = '192.168.1.99'
    hints['Nexus5x.lan'] = '192.168.1.124'
    hints['SonyDVD.lan'] = '192.168.1.118'
    hints['SonyTV.lan'] = '192.168.1.133'
    net.bufsize(4096)
    net.ipv4=true
    net.ipv6=true
    cache.open(30*MB)
    cache.clear()

    --- Included custom configuration file from: ---
    --- /etc/kresd/custom.conf
    root@turris:~# /etc/init.d/kresd restart
    root@turris:~# ping Foscam.lan
    ping: bad address 'Foscam.lan'
    root@turris:~# dig Ecobee3.lan

    ; <<>> DiG 9.9.8-P4 <<>> Ecobee3.lan
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39344
    ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;Ecobee3.lan.                   IN      A

    ;; AUTHORITY SECTION:
    .                       86400   IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2017011201 1800 900 604800 86400

    ;; Query time: 98 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Thu Jan 12 19:07:51 PST 2017
    ;; MSG SIZE  rcvd: 115

SOLVED
I found the problem.
Hints cannot begin with caps.

2

dns does not know caps

yet it would be interesting to reason why kres does not automatically convert

3

Hello.
I think only @vcunat can tell you why it doesn’t do it…

4

Yes, I saw this topic and put fixing it on my TODO list. There’s most likely no real reason, except that the implementer didn’t “notice that case”.

1 Like
5

this would be easier to swallow if the implementer woud not be employed(?) at a tld-registry.

beta-testing kres … erry day :wink:

6

Well, whatever :slight_smile: It’s now fixed in knot-resolver master.

7

Is there an issue with “-” in the host name?