Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - simervillefarm

#1
Just for the record I looked in the announcement section and it does provide some information on point release updates but what I am more looking for is more information on what what changed in the submodules.  As an example the anouncement section just mentioned "dhcp: improve compatibility with IPv6 deployments", what are these improvement(s)?

isc-dhcp42-server
4.2.7
4.2.8
isc-dhcp42-relay
4.2.7
4.2.8
isc-dhcp42-client
4.2.7
4.2.8
#2
I would like to know what changes/fixes are being implemented in the updates I am applying.  I am sure it is somewhere, I just can't seem to find it.
#3
Yes the entries I was testing (in this example) were static DNS entries that I had made, but the same holds true for dynamic entries as well.
#4
Oops , I messed up and I should have read the man pages.  For some reason I forgot to use the rDNS '-x' flag.  I feel shame and for the life of me I don't remember having to use the '-x' flag before, but obviously I did.  *sigh*  Oh well here is my expected output now.

Forwared lookup (ipv6)
mike@Karen:~$ dig AAAA backup.simervillefarm

; <<>> DiG 9.9.5-4.3ubuntu0.2-Ubuntu <<>> AAAA backup.simervillefarm
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44279
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;backup.simervillefarm. IN AAAA

;; ANSWER SECTION:
backup.simervillefarm. 3600 IN AAAA 2607:xxxx:y:zzzz::16

;; Query time: 2 msec
;; SERVER: 2607:xxxx:y:zzzz::1#53(2607:xxxx:y:zzzz::1)
;; WHEN: Sat Mar 21 08:59:30 EDT 2015
;; MSG SIZE  rcvd: 78

mike@Karen:~$


and the all important reverse DNS (ipv6)
mike@Karen:~$ dig -x 2607:xxxx:y:zzzz::16

; <<>> DiG 9.9.5-4.3ubuntu0.2-Ubuntu <<>> -x 2607:xxxx:y:zzzz::16
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32174
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;6.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.d.c.d.5.1.0.0.0.0.b.0.f.7.0.6.2.ip6.arpa. IN PTR

;; ANSWER SECTION:
6.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.d.c.d.5.1.0.0.0.0.b.0.f.7.0.6.2.ip6.arpa. 3600 IN PTR backup.simervillefarm.

;; Query time: 1 msec
;; SERVER: 2607:xxxx:y:zzzz::1#53(2607:xxxx:y:zzzz::1)
;; WHEN: Sat Mar 21 09:06:33 EDT 2015
;; MSG SIZE  rcvd: 136

mike@Karen:~$


Forwared lookup (ipv4)
mike@Karen:~$ dig backupv4.simervillefarm

; <<>> DiG 9.9.5-4.3ubuntu0.2-Ubuntu <<>> backupv4.simervillefarm
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42994
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
backupv4.simervillefarm. 3600 IN A 192.168.2.16

;; Query time: 1 msec
;; SERVER: 2607:xxxx:y:zzzz::1#53(2607:xxxx:y:zzzz::1)
;; WHEN: Sat Mar 21 09:10:11 EDT 2015
;; MSG SIZE  rcvd: 68

mike@Karen:~$


Reverse lookup (ipv4)
mike@Karen:~$ dig -x 192.168.2.16

; <<>> DiG 9.9.5-4.3ubuntu0.2-Ubuntu <<>> -x 192.168.2.16
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17222
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;16.2.168.192.in-addr.arpa. IN PTR

;; ANSWER SECTION:
16.2.168.192.in-addr.arpa. 3600 IN PTR backupv4.simervillefarm.

;; Query time: 1 msec
;; SERVER: 2607:xxxx:y:zzzz::1#53(2607:xxxx:y:zzzz::1)
;; WHEN: Sat Mar 21 09:11:08 EDT 2015
;; MSG SIZE  rcvd: 91

mike@Karen:~$
#5
Am I the only one out there with reverse lookup issues?  This has been killing me, I am going crazy trying to get DNS to work correctly.
#6
Hello all, I have setup an OPNSense (15.1.6.1) here on the farm to manage my Internet connection.  I am running a dual stack system so I can propagate IPV6 addresses to all my PLC devices here and be able to access them from the world.  I have almost everything working here with the exception of DNS.  Specifically reverse DNS.  I have DNS working by name but my reverse lookup is not.

IPV6
mike@Karen:~$ dig AAAA backup.simervillefarm

; <<>> DiG 9.9.5-4.3ubuntu0.1-Ubuntu <<>> AAAA backup.simervillefarm
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27144
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;backup.simervillefarm. IN AAAA

;; ANSWER SECTION:
backup.simervillefarm. 3600 IN AAAA 2607:xxxx:y:zzzz::16

;; Query time: 1 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Fri Feb 27 08:41:46 EST 2015
;; MSG SIZE  rcvd: 78

mike@Karen:~$ dig AAAA 2607:xxxx:y:zzzz::16

; <<>> DiG 9.9.5-4.3ubuntu0.1-Ubuntu <<>> AAAA 2607:xxxx:y:zzzz::16
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14585
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;2607:xxxx:y:zzzz::16. IN AAAA

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

;; Query time: 152 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Fri Feb 27 08:42:03 EST 2015
;; MSG SIZE  rcvd: 124

mike@Karen:~$


and IPV4
mike@Karen:~$ dig backupv4.simervillefarm

; <<>> DiG 9.9.5-4.3ubuntu0.1-Ubuntu <<>> backupv4.simervillefarm
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5243
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
backupv4.simervillefarm. 3600 IN A 192.168.2.16

;; Query time: 2 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Fri Feb 27 08:44:32 EST 2015
;; MSG SIZE  rcvd: 68

mike@Karen:~$ dig 192.168.2.16

; <<>> DiG 9.9.5-4.3ubuntu0.1-Ubuntu <<>> 192.168.2.16
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45870
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
192.168.2.16. 0 IN A 192.168.2.16

;; Query time: 0 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Fri Feb 27 08:44:49 EST 2015
;; MSG SIZE  rcvd: 57

mike@Karen:~$



I have scoured the OPNSense configuration pages and I can't see a spot to enable/disable reverse lookups (why there would be one I have no idea).  Anyone have any ideas where to start looking?

I guess another question would be why is there no answer section in the IPV6 reverse lookup query, I just noticed that now as I proof reading this.