Bind Forward Zone not Working

Clash Royale CLAN TAG#URR8PPP up vote
3
down vote
favorite
Running Ubuntu 18.04 LTS, and I am trying to configure Bind as a DNS server, for my home lab, as some of the software (VMware) requires DNS to run.
I have the reverse lookup working with issue, but forward lookup returns 0 answers. nslookup also fails to find the domain, and if I change this server to use itself for DNS in "/etc/resolv.conf", it has no network connectivity.
the contents of my bind configs are
named.conf
include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";
named.conf.options
acl "trusted"
10.0.1.90;
10.0.1.55;
10.0.1.57;
10.0.1.58;
10.0.1.100;
;
options
directory "/var/cache/bind";
recursion yes; # enables resursive queries
allow-recursion trusted; ; # allows recursive queries from "trusted" clients
listen-on 10.0.1.90; ; # ns1 private IP address - listen on private network only
allow-transfer none; ; # disable zone transfers by default
forwarders
10.0.1.1;
8.8.8.8;
8.8.8.4;
;
dnssec-validation no;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 any; ;
;
named.conf.local
zone "myhome.lan"
type master;
file "/etc/bind/for.myhome.lan";
;
zone "1.0.10.in-addr.arpa"
type master;
file "/etc/bind/rev.myhome.lan";
;
for.myhome.lan
$TTL 86400
@ IN SOA dns-01.myhome.lan. admin.myhome.lan. (
2018052102 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
; Name Servers - NS records
@ IN NS dns-01.myhome.lan.
; Name Servers - A Records
dns-01 IN A 10.0.1.90
; VMware
vcsa-01 IN A 10.0.1.100
esxi-01 IN A 10.0.1.55
esxi-02 IN A 10.0.1.57
esxi-03 IN A 10.0.1.58
rev.myhome.lan
$TTL 86400
@ IN SOA myhome.lan. admin.myhome.lan. (
2018052101 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
; Name Servers - NS records
@ IN NS dns-01.myhome.lan.
; Name Servers - A Records
dns-01 IN A 10.0.1.90
; PTR Records
90 IN PTR dns-01.myhome.lan.
100 IN PTR vcsa-01.myhome.lan.
55 IN PTR esxi-01.myhome.lan.
57 IN PTR esxi-02.myhome.lan.
58 IN PTR esxi-03.myhome.lan.
checking everything looks good
root@dns-01:/etc/bind# named-checkconf
root@dns-01:/etc/bind# named-checkzone myhome.lan for.myhome.lan
zone myhome.lan/IN: loaded serial 2018052102
OK
root@dns-01:/etc/bind# named-checkzone myhome.lan rev.myhome.lan
zone myhome.lan/IN: loaded serial 2018052101
OK
but dig and nslookup do not work
root@dns-01:/etc/bind# dig -x 10.0.1.90
; <<>> DiG 9.11.3-1ubuntu1-Ubuntu <<>> -x 10.0.1.90
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10718
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;90.1.0.10.in-addr.arpa. IN PTR
;; ANSWER SECTION:
90.1.0.10.in-addr.arpa. 0 IN PTR dns-01.
90.1.0.10.in-addr.arpa. 0 IN PTR dns-01.local.
;; Query time: 14 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon May 21 17:14:41 UTC 2018
;; MSG SIZE rcvd: 97
root@dns-01:/etc/bind# dig myhome.lan
; <<>> DiG 9.11.3-1ubuntu1-Ubuntu <<>> myhome.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51346
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;myhome.lan. IN A
;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon May 21 17:14:48 UTC 2018
;; MSG SIZE rcvd: 41
root@dns-01:/etc/bind# nslookup myhome.lan
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find myhome.lan: NXDOMAIN
I am banging my head against a wall, any help in identifying the problem would be greatly appreciated!
networking server 18.04 dns bind
 |Â
show 5 more comments
up vote
3
down vote
favorite
Running Ubuntu 18.04 LTS, and I am trying to configure Bind as a DNS server, for my home lab, as some of the software (VMware) requires DNS to run.
I have the reverse lookup working with issue, but forward lookup returns 0 answers. nslookup also fails to find the domain, and if I change this server to use itself for DNS in "/etc/resolv.conf", it has no network connectivity.
the contents of my bind configs are
named.conf
include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";
named.conf.options
acl "trusted"
10.0.1.90;
10.0.1.55;
10.0.1.57;
10.0.1.58;
10.0.1.100;
;
options
directory "/var/cache/bind";
recursion yes; # enables resursive queries
allow-recursion trusted; ; # allows recursive queries from "trusted" clients
listen-on 10.0.1.90; ; # ns1 private IP address - listen on private network only
allow-transfer none; ; # disable zone transfers by default
forwarders
10.0.1.1;
8.8.8.8;
8.8.8.4;
;
dnssec-validation no;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 any; ;
;
named.conf.local
zone "myhome.lan"
type master;
file "/etc/bind/for.myhome.lan";
;
zone "1.0.10.in-addr.arpa"
type master;
file "/etc/bind/rev.myhome.lan";
;
for.myhome.lan
$TTL 86400
@ IN SOA dns-01.myhome.lan. admin.myhome.lan. (
2018052102 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
; Name Servers - NS records
@ IN NS dns-01.myhome.lan.
; Name Servers - A Records
dns-01 IN A 10.0.1.90
; VMware
vcsa-01 IN A 10.0.1.100
esxi-01 IN A 10.0.1.55
esxi-02 IN A 10.0.1.57
esxi-03 IN A 10.0.1.58
rev.myhome.lan
$TTL 86400
@ IN SOA myhome.lan. admin.myhome.lan. (
2018052101 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
; Name Servers - NS records
@ IN NS dns-01.myhome.lan.
; Name Servers - A Records
dns-01 IN A 10.0.1.90
; PTR Records
90 IN PTR dns-01.myhome.lan.
100 IN PTR vcsa-01.myhome.lan.
55 IN PTR esxi-01.myhome.lan.
57 IN PTR esxi-02.myhome.lan.
58 IN PTR esxi-03.myhome.lan.
checking everything looks good
root@dns-01:/etc/bind# named-checkconf
root@dns-01:/etc/bind# named-checkzone myhome.lan for.myhome.lan
zone myhome.lan/IN: loaded serial 2018052102
OK
root@dns-01:/etc/bind# named-checkzone myhome.lan rev.myhome.lan
zone myhome.lan/IN: loaded serial 2018052101
OK
but dig and nslookup do not work
root@dns-01:/etc/bind# dig -x 10.0.1.90
; <<>> DiG 9.11.3-1ubuntu1-Ubuntu <<>> -x 10.0.1.90
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10718
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;90.1.0.10.in-addr.arpa. IN PTR
;; ANSWER SECTION:
90.1.0.10.in-addr.arpa. 0 IN PTR dns-01.
90.1.0.10.in-addr.arpa. 0 IN PTR dns-01.local.
;; Query time: 14 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon May 21 17:14:41 UTC 2018
;; MSG SIZE rcvd: 97
root@dns-01:/etc/bind# dig myhome.lan
; <<>> DiG 9.11.3-1ubuntu1-Ubuntu <<>> myhome.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51346
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;myhome.lan. IN A
;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon May 21 17:14:48 UTC 2018
;; MSG SIZE rcvd: 41
root@dns-01:/etc/bind# nslookup myhome.lan
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find myhome.lan: NXDOMAIN
I am banging my head against a wall, any help in identifying the problem would be greatly appreciated!
networking server 18.04 dns bind
First thing I would do is commenting the ACL until the server works and only then add the ACL back. That way you can determine if the ACL is the problem somehow or something else isn't working.
â Lienhart Woitok
May 21 at 17:41
Second, I realized that you are probably not asking your bind with these dig statements. Can you do them against bind directly? You have to add@10.0.1.90to the command.
â Lienhart Woitok
May 21 at 17:43
I commented the ACL out, and modified allow-recursion trusted; ; to allow-recursion any; ;, everything passed config testing, but no change in dig results.
â DrSeussFreak
May 21 at 17:44
because it is too long for a comment, see the screenshot below i.imgur.com/3aO7sMs.png
â DrSeussFreak
May 21 at 17:47
1
Well, in your zone there is no entry for "myhome.lan", try whatnslookup dns-01.myhome.landoes
â Lienhart Woitok
May 21 at 18:00
 |Â
show 5 more comments
up vote
3
down vote
favorite
up vote
3
down vote
favorite
Running Ubuntu 18.04 LTS, and I am trying to configure Bind as a DNS server, for my home lab, as some of the software (VMware) requires DNS to run.
I have the reverse lookup working with issue, but forward lookup returns 0 answers. nslookup also fails to find the domain, and if I change this server to use itself for DNS in "/etc/resolv.conf", it has no network connectivity.
the contents of my bind configs are
named.conf
include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";
named.conf.options
acl "trusted"
10.0.1.90;
10.0.1.55;
10.0.1.57;
10.0.1.58;
10.0.1.100;
;
options
directory "/var/cache/bind";
recursion yes; # enables resursive queries
allow-recursion trusted; ; # allows recursive queries from "trusted" clients
listen-on 10.0.1.90; ; # ns1 private IP address - listen on private network only
allow-transfer none; ; # disable zone transfers by default
forwarders
10.0.1.1;
8.8.8.8;
8.8.8.4;
;
dnssec-validation no;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 any; ;
;
named.conf.local
zone "myhome.lan"
type master;
file "/etc/bind/for.myhome.lan";
;
zone "1.0.10.in-addr.arpa"
type master;
file "/etc/bind/rev.myhome.lan";
;
for.myhome.lan
$TTL 86400
@ IN SOA dns-01.myhome.lan. admin.myhome.lan. (
2018052102 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
; Name Servers - NS records
@ IN NS dns-01.myhome.lan.
; Name Servers - A Records
dns-01 IN A 10.0.1.90
; VMware
vcsa-01 IN A 10.0.1.100
esxi-01 IN A 10.0.1.55
esxi-02 IN A 10.0.1.57
esxi-03 IN A 10.0.1.58
rev.myhome.lan
$TTL 86400
@ IN SOA myhome.lan. admin.myhome.lan. (
2018052101 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
; Name Servers - NS records
@ IN NS dns-01.myhome.lan.
; Name Servers - A Records
dns-01 IN A 10.0.1.90
; PTR Records
90 IN PTR dns-01.myhome.lan.
100 IN PTR vcsa-01.myhome.lan.
55 IN PTR esxi-01.myhome.lan.
57 IN PTR esxi-02.myhome.lan.
58 IN PTR esxi-03.myhome.lan.
checking everything looks good
root@dns-01:/etc/bind# named-checkconf
root@dns-01:/etc/bind# named-checkzone myhome.lan for.myhome.lan
zone myhome.lan/IN: loaded serial 2018052102
OK
root@dns-01:/etc/bind# named-checkzone myhome.lan rev.myhome.lan
zone myhome.lan/IN: loaded serial 2018052101
OK
but dig and nslookup do not work
root@dns-01:/etc/bind# dig -x 10.0.1.90
; <<>> DiG 9.11.3-1ubuntu1-Ubuntu <<>> -x 10.0.1.90
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10718
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;90.1.0.10.in-addr.arpa. IN PTR
;; ANSWER SECTION:
90.1.0.10.in-addr.arpa. 0 IN PTR dns-01.
90.1.0.10.in-addr.arpa. 0 IN PTR dns-01.local.
;; Query time: 14 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon May 21 17:14:41 UTC 2018
;; MSG SIZE rcvd: 97
root@dns-01:/etc/bind# dig myhome.lan
; <<>> DiG 9.11.3-1ubuntu1-Ubuntu <<>> myhome.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51346
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;myhome.lan. IN A
;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon May 21 17:14:48 UTC 2018
;; MSG SIZE rcvd: 41
root@dns-01:/etc/bind# nslookup myhome.lan
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find myhome.lan: NXDOMAIN
I am banging my head against a wall, any help in identifying the problem would be greatly appreciated!
networking server 18.04 dns bind
Running Ubuntu 18.04 LTS, and I am trying to configure Bind as a DNS server, for my home lab, as some of the software (VMware) requires DNS to run.
I have the reverse lookup working with issue, but forward lookup returns 0 answers. nslookup also fails to find the domain, and if I change this server to use itself for DNS in "/etc/resolv.conf", it has no network connectivity.
the contents of my bind configs are
named.conf
include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";
named.conf.options
acl "trusted"
10.0.1.90;
10.0.1.55;
10.0.1.57;
10.0.1.58;
10.0.1.100;
;
options
directory "/var/cache/bind";
recursion yes; # enables resursive queries
allow-recursion trusted; ; # allows recursive queries from "trusted" clients
listen-on 10.0.1.90; ; # ns1 private IP address - listen on private network only
allow-transfer none; ; # disable zone transfers by default
forwarders
10.0.1.1;
8.8.8.8;
8.8.8.4;
;
dnssec-validation no;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 any; ;
;
named.conf.local
zone "myhome.lan"
type master;
file "/etc/bind/for.myhome.lan";
;
zone "1.0.10.in-addr.arpa"
type master;
file "/etc/bind/rev.myhome.lan";
;
for.myhome.lan
$TTL 86400
@ IN SOA dns-01.myhome.lan. admin.myhome.lan. (
2018052102 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
; Name Servers - NS records
@ IN NS dns-01.myhome.lan.
; Name Servers - A Records
dns-01 IN A 10.0.1.90
; VMware
vcsa-01 IN A 10.0.1.100
esxi-01 IN A 10.0.1.55
esxi-02 IN A 10.0.1.57
esxi-03 IN A 10.0.1.58
rev.myhome.lan
$TTL 86400
@ IN SOA myhome.lan. admin.myhome.lan. (
2018052101 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
; Name Servers - NS records
@ IN NS dns-01.myhome.lan.
; Name Servers - A Records
dns-01 IN A 10.0.1.90
; PTR Records
90 IN PTR dns-01.myhome.lan.
100 IN PTR vcsa-01.myhome.lan.
55 IN PTR esxi-01.myhome.lan.
57 IN PTR esxi-02.myhome.lan.
58 IN PTR esxi-03.myhome.lan.
checking everything looks good
root@dns-01:/etc/bind# named-checkconf
root@dns-01:/etc/bind# named-checkzone myhome.lan for.myhome.lan
zone myhome.lan/IN: loaded serial 2018052102
OK
root@dns-01:/etc/bind# named-checkzone myhome.lan rev.myhome.lan
zone myhome.lan/IN: loaded serial 2018052101
OK
but dig and nslookup do not work
root@dns-01:/etc/bind# dig -x 10.0.1.90
; <<>> DiG 9.11.3-1ubuntu1-Ubuntu <<>> -x 10.0.1.90
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10718
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;90.1.0.10.in-addr.arpa. IN PTR
;; ANSWER SECTION:
90.1.0.10.in-addr.arpa. 0 IN PTR dns-01.
90.1.0.10.in-addr.arpa. 0 IN PTR dns-01.local.
;; Query time: 14 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon May 21 17:14:41 UTC 2018
;; MSG SIZE rcvd: 97
root@dns-01:/etc/bind# dig myhome.lan
; <<>> DiG 9.11.3-1ubuntu1-Ubuntu <<>> myhome.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51346
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;myhome.lan. IN A
;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon May 21 17:14:48 UTC 2018
;; MSG SIZE rcvd: 41
root@dns-01:/etc/bind# nslookup myhome.lan
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find myhome.lan: NXDOMAIN
I am banging my head against a wall, any help in identifying the problem would be greatly appreciated!
networking server 18.04 dns bind
asked May 21 at 17:17
DrSeussFreak
166
166
First thing I would do is commenting the ACL until the server works and only then add the ACL back. That way you can determine if the ACL is the problem somehow or something else isn't working.
â Lienhart Woitok
May 21 at 17:41
Second, I realized that you are probably not asking your bind with these dig statements. Can you do them against bind directly? You have to add@10.0.1.90to the command.
â Lienhart Woitok
May 21 at 17:43
I commented the ACL out, and modified allow-recursion trusted; ; to allow-recursion any; ;, everything passed config testing, but no change in dig results.
â DrSeussFreak
May 21 at 17:44
because it is too long for a comment, see the screenshot below i.imgur.com/3aO7sMs.png
â DrSeussFreak
May 21 at 17:47
1
Well, in your zone there is no entry for "myhome.lan", try whatnslookup dns-01.myhome.landoes
â Lienhart Woitok
May 21 at 18:00
 |Â
show 5 more comments
First thing I would do is commenting the ACL until the server works and only then add the ACL back. That way you can determine if the ACL is the problem somehow or something else isn't working.
â Lienhart Woitok
May 21 at 17:41
Second, I realized that you are probably not asking your bind with these dig statements. Can you do them against bind directly? You have to add@10.0.1.90to the command.
â Lienhart Woitok
May 21 at 17:43
I commented the ACL out, and modified allow-recursion trusted; ; to allow-recursion any; ;, everything passed config testing, but no change in dig results.
â DrSeussFreak
May 21 at 17:44
because it is too long for a comment, see the screenshot below i.imgur.com/3aO7sMs.png
â DrSeussFreak
May 21 at 17:47
1
Well, in your zone there is no entry for "myhome.lan", try whatnslookup dns-01.myhome.landoes
â Lienhart Woitok
May 21 at 18:00
First thing I would do is commenting the ACL until the server works and only then add the ACL back. That way you can determine if the ACL is the problem somehow or something else isn't working.
â Lienhart Woitok
May 21 at 17:41
First thing I would do is commenting the ACL until the server works and only then add the ACL back. That way you can determine if the ACL is the problem somehow or something else isn't working.
â Lienhart Woitok
May 21 at 17:41
Second, I realized that you are probably not asking your bind with these dig statements. Can you do them against bind directly? You have to add
@10.0.1.90 to the command.â Lienhart Woitok
May 21 at 17:43
Second, I realized that you are probably not asking your bind with these dig statements. Can you do them against bind directly? You have to add
@10.0.1.90 to the command.â Lienhart Woitok
May 21 at 17:43
I commented the ACL out, and modified allow-recursion trusted; ; to allow-recursion any; ;, everything passed config testing, but no change in dig results.
â DrSeussFreak
May 21 at 17:44
I commented the ACL out, and modified allow-recursion trusted; ; to allow-recursion any; ;, everything passed config testing, but no change in dig results.
â DrSeussFreak
May 21 at 17:44
because it is too long for a comment, see the screenshot below i.imgur.com/3aO7sMs.png
â DrSeussFreak
May 21 at 17:47
because it is too long for a comment, see the screenshot below i.imgur.com/3aO7sMs.png
â DrSeussFreak
May 21 at 17:47
1
1
Well, in your zone there is no entry for "myhome.lan", try what
nslookup dns-01.myhome.lan doesâ Lienhart Woitok
May 21 at 18:00
Well, in your zone there is no entry for "myhome.lan", try what
nslookup dns-01.myhome.lan doesâ Lienhart Woitok
May 21 at 18:00
 |Â
show 5 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Thanks to @LienhartWoitok, I removed the ACL and added this line to for.myhome.lan
@ IN A 10.0.1.90
This was needed as I was searching for myhome.lan only, and that was not specified anywhere. Adding that allowed me to search the domain itself.
by adding @10.0.1.90 to my dig commands, I forced searching to my domain. I now have a fully functional DNS server for my home lab!!!
Thanks @LienthartWoitok
You don't actually need the "@". See the Ubuntu Serverguide.
â Doug Smythies
May 21 at 18:19
doesn't hurt by being there though. Correct?
â DrSeussFreak
May 21 at 18:25
yes, i was just saying is all. The serverguide has both, but in my system I don't have both.
â Doug Smythies
May 21 at 18:47
Appreciate the heads-up, it is good to know it wasn't needed. I saw both in the examples I was following during setup.
â DrSeussFreak
May 21 at 20:16
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Thanks to @LienhartWoitok, I removed the ACL and added this line to for.myhome.lan
@ IN A 10.0.1.90
This was needed as I was searching for myhome.lan only, and that was not specified anywhere. Adding that allowed me to search the domain itself.
by adding @10.0.1.90 to my dig commands, I forced searching to my domain. I now have a fully functional DNS server for my home lab!!!
Thanks @LienthartWoitok
You don't actually need the "@". See the Ubuntu Serverguide.
â Doug Smythies
May 21 at 18:19
doesn't hurt by being there though. Correct?
â DrSeussFreak
May 21 at 18:25
yes, i was just saying is all. The serverguide has both, but in my system I don't have both.
â Doug Smythies
May 21 at 18:47
Appreciate the heads-up, it is good to know it wasn't needed. I saw both in the examples I was following during setup.
â DrSeussFreak
May 21 at 20:16
add a comment |Â
up vote
0
down vote
accepted
Thanks to @LienhartWoitok, I removed the ACL and added this line to for.myhome.lan
@ IN A 10.0.1.90
This was needed as I was searching for myhome.lan only, and that was not specified anywhere. Adding that allowed me to search the domain itself.
by adding @10.0.1.90 to my dig commands, I forced searching to my domain. I now have a fully functional DNS server for my home lab!!!
Thanks @LienthartWoitok
You don't actually need the "@". See the Ubuntu Serverguide.
â Doug Smythies
May 21 at 18:19
doesn't hurt by being there though. Correct?
â DrSeussFreak
May 21 at 18:25
yes, i was just saying is all. The serverguide has both, but in my system I don't have both.
â Doug Smythies
May 21 at 18:47
Appreciate the heads-up, it is good to know it wasn't needed. I saw both in the examples I was following during setup.
â DrSeussFreak
May 21 at 20:16
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Thanks to @LienhartWoitok, I removed the ACL and added this line to for.myhome.lan
@ IN A 10.0.1.90
This was needed as I was searching for myhome.lan only, and that was not specified anywhere. Adding that allowed me to search the domain itself.
by adding @10.0.1.90 to my dig commands, I forced searching to my domain. I now have a fully functional DNS server for my home lab!!!
Thanks @LienthartWoitok
Thanks to @LienhartWoitok, I removed the ACL and added this line to for.myhome.lan
@ IN A 10.0.1.90
This was needed as I was searching for myhome.lan only, and that was not specified anywhere. Adding that allowed me to search the domain itself.
by adding @10.0.1.90 to my dig commands, I forced searching to my domain. I now have a fully functional DNS server for my home lab!!!
Thanks @LienthartWoitok
answered May 21 at 18:17
DrSeussFreak
166
166
You don't actually need the "@". See the Ubuntu Serverguide.
â Doug Smythies
May 21 at 18:19
doesn't hurt by being there though. Correct?
â DrSeussFreak
May 21 at 18:25
yes, i was just saying is all. The serverguide has both, but in my system I don't have both.
â Doug Smythies
May 21 at 18:47
Appreciate the heads-up, it is good to know it wasn't needed. I saw both in the examples I was following during setup.
â DrSeussFreak
May 21 at 20:16
add a comment |Â
You don't actually need the "@". See the Ubuntu Serverguide.
â Doug Smythies
May 21 at 18:19
doesn't hurt by being there though. Correct?
â DrSeussFreak
May 21 at 18:25
yes, i was just saying is all. The serverguide has both, but in my system I don't have both.
â Doug Smythies
May 21 at 18:47
Appreciate the heads-up, it is good to know it wasn't needed. I saw both in the examples I was following during setup.
â DrSeussFreak
May 21 at 20:16
You don't actually need the "@". See the Ubuntu Serverguide.
â Doug Smythies
May 21 at 18:19
You don't actually need the "@". See the Ubuntu Serverguide.
â Doug Smythies
May 21 at 18:19
doesn't hurt by being there though. Correct?
â DrSeussFreak
May 21 at 18:25
doesn't hurt by being there though. Correct?
â DrSeussFreak
May 21 at 18:25
yes, i was just saying is all. The serverguide has both, but in my system I don't have both.
â Doug Smythies
May 21 at 18:47
yes, i was just saying is all. The serverguide has both, but in my system I don't have both.
â Doug Smythies
May 21 at 18:47
Appreciate the heads-up, it is good to know it wasn't needed. I saw both in the examples I was following during setup.
â DrSeussFreak
May 21 at 20:16
Appreciate the heads-up, it is good to know it wasn't needed. I saw both in the examples I was following during setup.
â DrSeussFreak
May 21 at 20:16
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1038775%2fbind-forward-zone-not-working%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
First thing I would do is commenting the ACL until the server works and only then add the ACL back. That way you can determine if the ACL is the problem somehow or something else isn't working.
â Lienhart Woitok
May 21 at 17:41
Second, I realized that you are probably not asking your bind with these dig statements. Can you do them against bind directly? You have to add
@10.0.1.90to the command.â Lienhart Woitok
May 21 at 17:43
I commented the ACL out, and modified allow-recursion trusted; ; to allow-recursion any; ;, everything passed config testing, but no change in dig results.
â DrSeussFreak
May 21 at 17:44
because it is too long for a comment, see the screenshot below i.imgur.com/3aO7sMs.png
â DrSeussFreak
May 21 at 17:47
1
Well, in your zone there is no entry for "myhome.lan", try what
nslookup dns-01.myhome.landoesâ Lienhart Woitok
May 21 at 18:00