What the requests look like on failure
** Attachment added: bind9-failure.out
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1101002/+attachment/3504879/+files/bind9-failure.out
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Ran `ping something.dev` until it stopped failing, and here is the
output of your 3 tests on success (just in case, for comparison)
** Attachment added: bind9-success.out
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1101002/+attachment/3504880/+files/bind9-success.out
--
You
Content of resolv.conf
** Attachment added: resolv.conf
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1101002/+attachment/3504882/+files/resolv.conf
** Changed in: bind9 (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
What the requests look like on failure
** Attachment added: bind9-failure.out
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1101002/+attachment/3504879/+files/bind9-failure.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ran `ping something.dev` until it stopped failing, and here is the
output of your 3 tests on success (just in case, for comparison)
** Attachment added: bind9-success.out
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1101002/+attachment/3504880/+files/bind9-success.out
--
You
Content of resolv.conf
** Attachment added: resolv.conf
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1101002/+attachment/3504882/+files/resolv.conf
** Changed in: bind9 (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
I've provided the information requested - if there is anything else I
can provide, please let me know. I did this after a reboot, so the
issue may not have arisen in the logs yet. Right?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I've provided the information requested - if there is anything else I
can provide, please let me know. I did this after a reboot, so the
issue may not have arisen in the logs yet. Right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: KernLog.txt
https://bugs.launchpad.net/bugs/1101002/+attachment/3487655/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
apport information
** Tags added: apport-collected quantal
** Description changed:
- I'm not the only one experiencing this issue in the office. I've set up
- *.dev to point to 127.0.0.1 following the steps here:
- http://groups.drupal.org/node/16862. Usually when I ping
- something.dev, it
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1101002/+attachment/3487656/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
apport information
** Tags added: apport-collected quantal
** Description changed:
- I'm not the only one experiencing this issue in the office. I've set up
- *.dev to point to 127.0.0.1 following the steps here:
- http://groups.drupal.org/node/16862. Usually when I ping
- something.dev, it
apport information
** Attachment added: KernLog.txt
https://bugs.launchpad.net/bugs/1101002/+attachment/3487655/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101002
Title:
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1101002/+attachment/3487656/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101002
Public bug reported:
I'm not the only one experiencing this issue in the office. I've set up
*.dev to point to 127.0.0.1 following the steps here:
http://groups.drupal.org/node/16862. Usually when I ping
something.dev, it works, but sometimes it fails. I can hit
something.dev:80 repeatedly
Public bug reported:
I'm not the only one experiencing this issue in the office. I've set up
*.dev to point to 127.0.0.1 following the steps here:
http://groups.drupal.org/node/16862. Usually when I ping
something.dev, it works, but sometimes it fails. I can hit
something.dev:80 repeatedly
16 matches
Mail list logo