Hi folks,
I have finally resolved my issue with docker interface.I had to delete my
Ubuntu and install a brand new Centos on my server.Now everything works as
expected.
Cheers
Em sábado, 7 de maio de 2022 06:23:32 GMT+1, Nick Tait via bind-users
escreveu:
On 7/05/2022 1:38 am, MaurÃ
On 7/05/2022 1:38 am, Maurà cio Penteado via bind-users wrote:
I added the A-record "ns1 IN A 172.17.0.1" to my zone-file as
suggested and it seems that the order fixed the issue.
Now my Bind9 clients are getting ip 192.168.0.10 favorably.
Hi Mauricio.
I don't think anyone suggested that
I just message you and the problem happened again ...
C:\Users\Mauricioλ ping ns1.example.lan
Pinging ns1.example.lan [172.17.0.1] with 32 bytes of data:Reply from
84.116.236.63: Destination net unreachable.Reply from 84.116.236.63:
Destination net unreachable.Reply from 84.116.236.63:
Hi folks,
Thank you for the reply.
I added the A-record "ns1 IN A 172.17.0.1" to my zone-file as suggested and
it seems that the order fixed the issue.Now my Bind9 clients are getting ip
192.168.0.10 favorably.
Anyway, I'd like to eliminate ip 172.17.0.1 from name resolutions.I never added
On 6/05/2022 7:51 am, Grant Taylor via bind-users wrote:
On my Bind9 server, I have the following zone-files:
forward.example.lan.db:
ns1 IN A 192.168.0.10
ns1 IN fe80::f21f:afff:fe5d:be90
I don't see the 2nd, Docker (?), address; 172.17.0.1, in the zone.
On 5/5/22 1:35 PM, Maurà cio Penteado via bind-users wrote:
Hi folks,
Hi,
Thank you for the reply.
:-)
Unfortunately, I did not understand how I am supposed to add multiple
A-records for the same name to the zone-file to fix this issue.
Based on your first message, you already have
Hi folks,
Thank you for the reply.
Unfortunately, I did not understand how I am supposed to add multiple A-records
for the same name to the zone-file to fix this issue.
On my Bind9 server, I have the following zone-files:
- - -
forward.example.lan.db:
$TTL 604800@ IN SOA
On 5/5/22 9:01 AM, Reindl Harald wrote:
by not add multiple A-records for the same name to the zone-file
BIND don't know about docker on it's own
Another option would be to leverage BIND's ability to sort A records
based on configured preference (in the config file, not the zone file)
based
Am 05.05.22 um 16:05 schrieb Maurà cio Penteado via bind-users:
What is the current behavior?
Nslookup from a DNS Client workstation should not get docker0 ip
addrees of the Bind9 Server PC.
|nslookup ns1.example.lan Server: UnKnown Address:
fe80::f21f:afff:fe5d:be90 Name:
Summary
Docker0 interface is being resolved and DNS Clients cannot deal with the
address.
BIND version used
BIND 9.18.1-1ubuntu1-Ubuntu (Stable Release)
Steps to reproduce
On a fresh Ubuntu 22.04 Server install and set Bind9 up. After that install
docker.
What is the current behavior?
10 matches
Mail list logo
