ubuntu-ca Digest, Vol 43, Issue 24
Ralph Pichie
thevillagegeek at gmail.com
Sun Oct 19 17:17:54 UTC 2008
Thanks. I'll try that when I get a chance. Looking forward to editing
Vista out of my boot menu entirely...
On Sun, Oct 19, 2008 at 5:00 AM, <ubuntu-ca-request at lists.ubuntu.com> wrote:
> Send ubuntu-ca mailing list submissions to
> ubuntu-ca at lists.ubuntu.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-ca
> or, via email, send a message with subject or body 'help' to
> ubuntu-ca-request at lists.ubuntu.com
>
> You can reach the person managing the list at
> ubuntu-ca-owner at lists.ubuntu.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ubuntu-ca digest..."
>
>
> Today's Topics:
>
> 1. Re: Why DNS query shows different result for some hours?
> (Ralph Janke)
> 2. kernel kraziness (Ralph Pichie)
> 3. Re: kernel kraziness (Andy Boersma)
> 4. Re: kernel kraziness (Andy Boersma)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 18 Oct 2008 12:13:03 -0400
> From: Ralph Janke <txwikinger at ubuntu.com>
> Subject: Re: Why DNS query shows different result for some hours?
> To: The Canadian Ubuntu Users Community <ubuntu-ca at lists.ubuntu.com>
> Message-ID: <48FA0B0F.904 at ubuntu.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Well,
>
> you need to be sure that the DNS servers are synced. Maybe
> you should look into some public DNS servers that allow
> dynamic IPs. IIRC dyndns.org offers something like that.
> I do not know how complicated your DNS records are,
> but simple solutions are probably free with dyndns.
>
> Hope this helps,
>
> -Ralph
>
> Corman 4u wrote:
>> Thanks, Ralph.
>>
>> I think you got the right point. Your comment is very helpful.
>>
>> There is no communication between my own DNS server and
>> DNS servers from the public service provider. (hereinafter public DNS)
>> When I registered my domain, I regiestered public DNSs for the domain name record.
>> Then my domain had a parking page such as Under construction'.
>> I am using dynamic IP, but it is almost like the static IP.
>> I've never seen my IP changed. I think it is because I am using the router, which I've never turned off.
>> Now I built my own DNS server on my machine and home page.
>> I registered my own DNS server in the domain name record (primary) and changed public DNSs into secondary and ternary because I didn't have my own secondary DNS.
>>
>> I expected that my DNS server worked well because it is now primary,
>> as long as I don't turned off my machine and the router.
>> When my IP is changed or my machine is interruted, then access to my domain will be forwarded
>> to the previous parking page. (different IP address in each authority section)
>>
>> Client's access to my domain --> client's DNS request to get the domain name record --> national DNS provides my DNS server IP if available --> client's DNS request to my own DNS server--> my own DNS server provides info of IP address
>>
>>
>> My dynamic IP is still the same. Synchnonization between public DNSs (my secondary and ternary) is sure;
>> however, not between my own DNS and public DNS servers.
>> I cannot change public DNS server
>> s record with my dynamic IP address.
>> In order to fulfill my intention, should I build my own secondary DNS and is it the only way?
>>
>>
>> Corman
>>
>> 2008/10/17 Ralph Janke <txwikinger at ubuntu.com>
>>
>>> I am not 100% sure that I understand what you say.
>>>
>>> As I understand it, you have configured your domain name
>>> record to have your own machine as the first DNS server,
>>> and a server from a public service provider as the second.
>>>
>>> I do not understand if the DNS records for your domain between
>>> the two are synced. If not this needs to be done.
>>>
>>> DNS works in a redundant way. DNS servers will get the information
>>> from any one of the DNS servers that are in the domain name record.
>>> Therefore all DNS servers configured must have the same information.
>>> This can usually be done by configuring one primary and the other ones
>>> as secondary severs. However, I am not sure if you can do that in your
>>> situation.
>>>
>>> Then it is irrelevant which server is named in the authority section.
>>>
>>> However, it almost looks to me that your own machine is not always
>>> available to the outside and the other server does not have the right
>>> information.
>>>
>>> If you want to, you can send me to my email privately the information
>>> how you have set everything up, and I can have a look.
>>>
>>> Hope this helps,
>>>
>>> - Ralph
>>>
>>>
>>>
>>> Corman 4u wrote:
>>>
>>>> I have had a domain name and set up with 2 DNS servers from a public service
>>>> provider.
>>>> Recently, I changed one of DNS servers with my IP, which has my own DNS on
>>>> LINUX.
>>>> So first DNS of the domain is my DNS server and the second is one of DNS
>>>> servers of the public service provider.
>>>> When I query the domain, sometimes it works for hours; dig command shows my
>>>> IP in Answer Section.
>>>> But sometimes it doesn't work; dig command shows my IP (my DNS) or the DNS
>>>> server of the business service alternatively.
>>>> This situation is repeating for several days; it works well for several
>>>> hours, but doesn't for the next several hours.
>>>> While DNS query shows different result at each query, outside clients get
>>>> Gateway Timeout with code=DNS_TIMEOUT.
>>>> Is there anybody who knows the reason and how to fix this problem?
>>>>
>>>> Corman
>>>>
>>>>
>>>>
>>> --
>>> ubuntu-ca mailing list
>>> ubuntu-ca at lists.ubuntu.com
>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-ca
>>>
>>
>>
>>
>>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: https://lists.ubuntu.com/archives/ubuntu-ca/attachments/20081018/51dad0ae/attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Sat, 18 Oct 2008 18:55:52 -0600
> From: "Ralph Pichie" <thevillagegeek at gmail.com>
> Subject: kernel kraziness
> To: ubuntu-ca at lists.ubuntu.com
> Message-ID:
> <a65bfad00810181755i489fd066ubfc5542a550dad1c at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Early Friday, I did a major update on my main laptop, including some
> some very essential packages. Later that day, I found that my wifi
> card did not work anymore and that I had to reinstall madwifi.
> Fortunately, I had saved the instructions in my Tomboy notes and was
> soon good-to-go, or so I thought.
>
> Attempting to reboot again, I found that Ubuntu 8.04 would no longer
> start, even in recovery mode, until I rebooted and chose an older
> kernel as a boot option. I have since edited my Grub menu so that the
> older kernel is the default choice.
>
> While the system is functioning, I'd like to use a more current
> kernel. Any ideas what might be wrong and how to fix it?
>
> My computer is an Acer Aspire 5315-2176, dual booted with Winbloze
> Vista and Ubuntu 8.04. I use madwifi to handle the proprietary
> wireless.
>
> the relevant section of my menu.lst file reads like so
>
>
> title Ubuntu 8.04.1, kernel 2.6.24-19-generic
> root (hd0,4)
> kernel /boot/vmlinuz-2.6.24-19-generic
> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro quiet splash
> initrd /boot/initrd.img-2.6.24-19-generic
> quiet
>
> title Ubuntu 8.04.1, kernel 2.6.24-19-generic (recovery mode)
> root (hd0,4)
> kernel /boot/vmlinuz-2.6.24-19-generic
> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro single
> initrd /boot/initrd.img-2.6.24-19-generic
>
>
> title Ubuntu 8.04.1, kernel 2.6.24-21-generic
> root (hd0,4)
> kernel /boot/vmlinuz-2.6.24-21-generic
> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro quiet splash
> initrd /boot/initrd.img-2.6.24-21-generic
> quiet
>
> title Ubuntu 8.04.1, kernel 2.6.24-21-generic (recovery mode)
> root (hd0,4)
> kernel /boot/vmlinuz-2.6.24-21-generic
> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro single
> initrd /boot/initrd.img-2.6.24-21-generic
>
> title Ubuntu 8.04.1, kernel 2.6.24-16-generic
> root (hd0,4)
> kernel /boot/vmlinuz-2.6.24-16-generic
> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro quiet splash
> initrd /boot/initrd.img-2.6.24-16-generic
> quiet
>
> title Ubuntu 8.04.1, kernel 2.6.24-16-generic (recovery mode)
> root (hd0,4)
> kernel /boot/vmlinuz-2.6.24-16-generic
> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro single
> initrd /boot/initrd.img-2.6.24-16-generic
>
> title Ubuntu 8.04.1, memtest86+
> root (hd0,4)
> kernel /boot/memtest86+.bin
> quiet
>
> ### END DEBIAN AUTOMAGIC KERNELS LIST
>
> # This is a divider, added to separate the menu items below from the Debian
> # ones.
> title Other operating systems:
> root
>
>
> # This entry automatically added by the Debian installer for a non-linux OS
> # on /dev/sda1
> title Windows Vista/Longhorn (loader)
> root (hd0,0)
> savedefault
> makeactive
> chainloader +1
>
>
> # This entry automatically added by the Debian installer for a non-linux OS
> # on /dev/sda2
> title Windows Vista/Longhorn (loader)
> root (hd0,1)
> savedefault
> makeactive
> chainloader +1
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 18 Oct 2008 21:32:44 -0400
> From: Andy Boersma <andy at boersma.ca>
> Subject: Re: kernel kraziness
> To: The Canadian Ubuntu Users Community <ubuntu-ca at lists.ubuntu.com>
> Message-ID: <48FA8E3C.3000307 at boersma.ca>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> after the last update I had to manually re-add the wireless drivers
> in the driver directory.
>
> make
> sudo make install
> sudo modprobe ath_pci
>
> And everything worked after a reboot.
>
>
>
> Ralph Pichie wrote:
>> Early Friday, I did a major update on my main laptop, including some
>> some very essential packages. Later that day, I found that my wifi
>> card did not work anymore and that I had to reinstall madwifi.
>> Fortunately, I had saved the instructions in my Tomboy notes and was
>> soon good-to-go, or so I thought.
>>
>> Attempting to reboot again, I found that Ubuntu 8.04 would no longer
>> start, even in recovery mode, until I rebooted and chose an older
>> kernel as a boot option. I have since edited my Grub menu so that the
>> older kernel is the default choice.
>>
>> While the system is functioning, I'd like to use a more current
>> kernel. Any ideas what might be wrong and how to fix it?
>>
>> My computer is an Acer Aspire 5315-2176, dual booted with Winbloze
>> Vista and Ubuntu 8.04. I use madwifi to handle the proprietary
>> wireless.
>>
>> the relevant section of my menu.lst file reads like so
>>
>>
>> title Ubuntu 8.04.1, kernel 2.6.24-19-generic
>> root (hd0,4)
>> kernel /boot/vmlinuz-2.6.24-19-generic
>> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro quiet splash
>> initrd /boot/initrd.img-2.6.24-19-generic
>> quiet
>>
>> title Ubuntu 8.04.1, kernel 2.6.24-19-generic (recovery mode)
>> root (hd0,4)
>> kernel /boot/vmlinuz-2.6.24-19-generic
>> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro single
>> initrd /boot/initrd.img-2.6.24-19-generic
>>
>>
>> title Ubuntu 8.04.1, kernel 2.6.24-21-generic
>> root (hd0,4)
>> kernel /boot/vmlinuz-2.6.24-21-generic
>> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro quiet splash
>> initrd /boot/initrd.img-2.6.24-21-generic
>> quiet
>>
>> title Ubuntu 8.04.1, kernel 2.6.24-21-generic (recovery mode)
>> root (hd0,4)
>> kernel /boot/vmlinuz-2.6.24-21-generic
>> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro single
>> initrd /boot/initrd.img-2.6.24-21-generic
>>
>> title Ubuntu 8.04.1, kernel 2.6.24-16-generic
>> root (hd0,4)
>> kernel /boot/vmlinuz-2.6.24-16-generic
>> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro quiet splash
>> initrd /boot/initrd.img-2.6.24-16-generic
>> quiet
>>
>> title Ubuntu 8.04.1, kernel 2.6.24-16-generic (recovery mode)
>> root (hd0,4)
>> kernel /boot/vmlinuz-2.6.24-16-generic
>> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro single
>> initrd /boot/initrd.img-2.6.24-16-generic
>>
>> title Ubuntu 8.04.1, memtest86+
>> root (hd0,4)
>> kernel /boot/memtest86+.bin
>> quiet
>>
>> ### END DEBIAN AUTOMAGIC KERNELS LIST
>>
>> # This is a divider, added to separate the menu items below from the Debian
>> # ones.
>> title Other operating systems:
>> root
>>
>>
>> # This entry automatically added by the Debian installer for a non-linux OS
>> # on /dev/sda1
>> title Windows Vista/Longhorn (loader)
>> root (hd0,0)
>> savedefault
>> makeactive
>> chainloader +1
>>
>>
>> # This entry automatically added by the Debian installer for a non-linux OS
>> # on /dev/sda2
>> title Windows Vista/Longhorn (loader)
>> root (hd0,1)
>> savedefault
>> makeactive
>> chainloader +1
>>
>>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 18 Oct 2008 21:35:38 -0400
> From: Andy Boersma <andy at boersma.ca>
> Subject: Re: kernel kraziness
> To: The Canadian Ubuntu Users Community <ubuntu-ca at lists.ubuntu.com>
> Message-ID: <48FA8EEA.5020504 at boersma.ca>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Sorry wrong notes
> this is correct, in the driver directory
>
> make clean
> make
> sudo make install
>
>
>
> Ralph Pichie wrote:
>> Early Friday, I did a major update on my main laptop, including some
>> some very essential packages. Later that day, I found that my wifi
>> card did not work anymore and that I had to reinstall madwifi.
>> Fortunately, I had saved the instructions in my Tomboy notes and was
>> soon good-to-go, or so I thought.
>>
>> Attempting to reboot again, I found that Ubuntu 8.04 would no longer
>> start, even in recovery mode, until I rebooted and chose an older
>> kernel as a boot option. I have since edited my Grub menu so that the
>> older kernel is the default choice.
>>
>> While the system is functioning, I'd like to use a more current
>> kernel. Any ideas what might be wrong and how to fix it?
>>
>> My computer is an Acer Aspire 5315-2176, dual booted with Winbloze
>> Vista and Ubuntu 8.04. I use madwifi to handle the proprietary
>> wireless.
>>
>> the relevant section of my menu.lst file reads like so
>>
>>
>> title Ubuntu 8.04.1, kernel 2.6.24-19-generic
>> root (hd0,4)
>> kernel /boot/vmlinuz-2.6.24-19-generic
>> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro quiet splash
>> initrd /boot/initrd.img-2.6.24-19-generic
>> quiet
>>
>> title Ubuntu 8.04.1, kernel 2.6.24-19-generic (recovery mode)
>> root (hd0,4)
>> kernel /boot/vmlinuz-2.6.24-19-generic
>> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro single
>> initrd /boot/initrd.img-2.6.24-19-generic
>>
>>
>> title Ubuntu 8.04.1, kernel 2.6.24-21-generic
>> root (hd0,4)
>> kernel /boot/vmlinuz-2.6.24-21-generic
>> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro quiet splash
>> initrd /boot/initrd.img-2.6.24-21-generic
>> quiet
>>
>> title Ubuntu 8.04.1, kernel 2.6.24-21-generic (recovery mode)
>> root (hd0,4)
>> kernel /boot/vmlinuz-2.6.24-21-generic
>> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro single
>> initrd /boot/initrd.img-2.6.24-21-generic
>>
>> title Ubuntu 8.04.1, kernel 2.6.24-16-generic
>> root (hd0,4)
>> kernel /boot/vmlinuz-2.6.24-16-generic
>> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro quiet splash
>> initrd /boot/initrd.img-2.6.24-16-generic
>> quiet
>>
>> title Ubuntu 8.04.1, kernel 2.6.24-16-generic (recovery mode)
>> root (hd0,4)
>> kernel /boot/vmlinuz-2.6.24-16-generic
>> root=UUID=e73a8c60-84c4-42d1-9905-e7297aa3922d ro single
>> initrd /boot/initrd.img-2.6.24-16-generic
>>
>> title Ubuntu 8.04.1, memtest86+
>> root (hd0,4)
>> kernel /boot/memtest86+.bin
>> quiet
>>
>> ### END DEBIAN AUTOMAGIC KERNELS LIST
>>
>> # This is a divider, added to separate the menu items below from the Debian
>> # ones.
>> title Other operating systems:
>> root
>>
>>
>> # This entry automatically added by the Debian installer for a non-linux OS
>> # on /dev/sda1
>> title Windows Vista/Longhorn (loader)
>> root (hd0,0)
>> savedefault
>> makeactive
>> chainloader +1
>>
>>
>> # This entry automatically added by the Debian installer for a non-linux OS
>> # on /dev/sda2
>> title Windows Vista/Longhorn (loader)
>> root (hd0,1)
>> savedefault
>> makeactive
>> chainloader +1
>>
>>
>
>
>
> ------------------------------
>
> --
> ubuntu-ca mailing list
> ubuntu-ca at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-ca
>
>
> End of ubuntu-ca Digest, Vol 43, Issue 24
> *****************************************
>
More information about the ubuntu-ca
mailing list