[Bug 1787739] Re: postfix name lookup failed after dist-upgrade (Aug-2018)

2018-09-10 Thread Mike Dotson
Why is this incomplete? What additional information is needed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787739 Title: postfix name lookup failed after dist-upgrade (Aug-2018) To manage notif

[Bug 1787739] Re: postfix name lookup failed after dist-upgrade (Aug-2018)

2018-09-11 Thread Mike Dotson
Unfortunately not seeing a comment. I did include a vagrant file that should reproduce the issue. I found a work around for postfix but the nslookup issue is still there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.l

[Bug 1787739] Re: postfix name lookup failed after dist-upgrade (Aug-2018)

2018-09-11 Thread Mike Dotson
Fixed ip addresses in vagrant file ** Attachment added: "Vagrantfile" https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1787739/+attachment/5187722/+files/Vagrantfile -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs

[Bug 1787739] Re: postfix name lookup failed after dist-upgrade (Aug-2018)

2018-09-11 Thread Mike Dotson
First, I want to apologize, the Vagrant file I uploaded was apparently the incorrect one. I'm attaching the version I'm testing with. I actually found this with my internal server running as an LXD container. With my options file set to the following (192.168.0.130 eth0 address): options {

[Bug 1787739] Re: postfix name lookup failed after dist-upgrade (Aug-2018)

2018-10-18 Thread Mike Dotson
I'll see if I can get a chance to do some packet captures later this week, however, I did notice something that may be relevant. The domains that seem to fail do not have IPV6 look addresses. The domains that succeed have IPV6 address returns: vagrant@ubuntu-bionic:~$ nslookup google.com Server:

[Bug 1787739] Re: postfix name lookup failed after dist-upgrade (Aug-2018)

2018-10-18 Thread Mike Dotson
Same results using the vagrant vm configured bind server: vagrant@ubuntu-bionic:~$ nslookup ubuntu.com - 192.168.0.130 Server: 192.168.0.130 Address:192.168.0.130#53 Non-authoritative answer: Name: ubuntu.com Address: 91.189.94.40 ** server can't find ubuntu.com: SERVFAIL vagra

[Bug 1787739] Re: postfix name lookup failed after dist-upgrade (Aug-2018)

2018-10-03 Thread Mike Dotson
Was the previous debug information helpful or will you need additional information? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787739 Title: postfix name lookup failed after dist-upgrade (Aug-20

[Bug 1872896] Re: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04)

2020-06-17 Thread Mike Dotson
Installing vim package resolves the issue of `vi empty`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872896 Title: terminfo file xterm-256color has entries that make vi unusable when sshing in

[Bug 1787739] [NEW] postfix name lookup failed after dist-upgrade (Aug-2018)

2018-08-18 Thread Mike Dotson
Public bug reported: Internal DNS cache configured on LXD system: Upon further investigation, nslookup is having similar issues: 18.04 LTS system: # nslookup oracle.com - 192.168.0.30 Server: 192.168.0.30 Address:192.168.0.30#53 Non-authoritative answer: Name: oracle.com Addre

[Bug 1787739] Re: postfix name lookup failed after dist-upgrade (Aug-2018)

2018-08-20 Thread Mike Dotson
Attaching Vagrant file to duplicate issue ** Attachment added: "Vagrant file to reproduce issue" https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1787739/+attachment/5178386/+files/Vagrantfile -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscr