Re: DNS problem -
On 11/12/2013 10:13 PM, Tim issued this missive: Bob Goodwin: I changed the router configuration to use 208.67.229.220:5353 and 208.67.222.222:5353 and see the following: [root@box10 bobg]# dig www.bbc.co.uk ; <<>> DiG 9.9.3-rl.13207.22-P2-RedHat-9.9.3-5.P2.fc19 <<>> www.bbc.co.uk ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35870 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.bbc.co.uk.INA ;; ANSWER SECTION: www.bbc.co.uk.176INCNAMEwww.bbc.net.uk. www.bbc.net.uk.182INA212.58.246.93 www.bbc.net.uk.182INA212.58.246.92 ;; Query time: 616 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Tue Nov 12 11:46:20 EST 2013 ;; MSG SIZE rcvd: 100 As you say the cache is much faster, 2 ms as opposed to 616 ms. But I still don't know what DNS address it actually goes to, how do I find that? Just to be clear, DNS means domain name *system* not *server*. So, are you asking you're not sure what DNS server has responded, or you don't know how to read the answers you got back from dig? Looking at your above dig results: Your command line asked whatever your computer's default DNS server was (configured in /etc/resolv.conf) to look up www.bbc.co.uk. The ANSWER section gives results about your query addresses. A query for www.bbc.co.uk gets a CNAME answer of www.bbc.net.uk (i.e. it says use that second name, instead). Followed by two answers for IPs for www.bbc.net.uk, saying to use either 212.58.246.93 or 212.58.246.92 (either will do). The QUERY TIME section says the server that answered was 192.168.1.1, so that would be the first DNS server address in your /etc/resolv.conf file. Second or third server addresses in that config file will only be consulted if the first one failed to respond, and there'd be a seriously long time-out period before that happened. Your router, at 192.168.1.1 may have tried to query 208.67.229.220:5353 and 208.67.222.222:5353 to find the results (I don't know if your router/modem can accept port numbers attached to the IPs, like that), and may have connected to them. Or, your ISP may have intercepted that. You might try using those IPs and ports with the dig command, directly. By default, dig will use your pre-configured DNS servers (in your /etc/resolv.conf file) unless you specify a server to query on its command line. That is *which* server to ask, not just what address you want to look up. If you want to use dig to query a DNS server that is NOT in your /etc/resolv.conf file, use something like: dig @208.67.229.220 -p 5353 www.bbc.co.uk The "@ip-address" would be the address of the DNS server you want to query. If you don't want to use the standard DNS port of 53, then include the "-p " with "" the non-standard port number to use (e.g. port 5353 in this example). See "man dig" for other options. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - Diplomacy: The art of saying "Nice doggy!" until you can find a - -big enough rock.- -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On Wed, 2013-11-13 at 11:03 +1100, Cameron Simpson wrote: > Maybe, maybe not. If one of their DNS servers was flakey, your > complaint would not be alone. If they replaced/repaired their server, > everyone will see the fix. > > And the front line phone staff may be unaware of the issue. It depends on the ISP. I can mention two major ones in this country, Optus and Telstra, who don't just service customers, but are backbones for most other smaller ISPs, who will flatly refuse to admit that there's ever anything wrong with their equipment, will endlessly tell you reset your equipment, despite all evidence to the contrary that their system is up the creek - e.g. their support newsgroup is full of customers complaining that the DNS server isn't working. So I am as dismissive of anything they say, as they are of their customer complaints (they're as arrogant as that against their phone customers, as well). I could mention an older ISP that doesn't exist anymore, Picknowl, that would get back to your support query and say they've checked their equipment, noticed something wrong and reset it, or didn't find a problem but reset it just in case. And, back in the dialup days, if you had trouble connecting, they'd ask you to dial a specific number, and they'd watch their terminal to check what your system was trying to do as it logged in. I had more faith in them. Unfortunately, they got bought out and ruined. Another ISP (Adam) seems to publish their internal fault reports on their status pages. You can see fault history, scheduled maintenance, reported faults, and expected repair times. It's usually kept up to date quite promptly. But if you're going to make a fault report to an ISP, with any hope of getting a proper response, you need to make a proper report that they can follow up on. Mention your own IP, addresses you've tried to access but failed, your time and timezone - so they can check their logs, not just their equipment at the current moment. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
Bob Goodwin: > I changed the router configuration to use 208.67.229.220:5353 and > 208.67.222.222:5353 and see the following: > > [root@box10 bobg]# dig www.bbc.co.uk > > ; <<>> DiG 9.9.3-rl.13207.22-P2-RedHat-9.9.3-5.P2.fc19 <<>> www.bbc.co.uk > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35870 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 4096 > ;; QUESTION SECTION: > ;www.bbc.co.uk.INA > > ;; ANSWER SECTION: > www.bbc.co.uk.176INCNAMEwww.bbc.net.uk. > www.bbc.net.uk.182INA212.58.246.93 > www.bbc.net.uk.182INA212.58.246.92 > > ;; Query time: 616 msec > ;; SERVER: 192.168.1.1#53(192.168.1.1) > ;; WHEN: Tue Nov 12 11:46:20 EST 2013 > ;; MSG SIZE rcvd: 100 > > As you say the cache is much faster, 2 ms as opposed to 616 ms. > > But I still don't know what DNS address it actually goes to, how do I > find that? Just to be clear, DNS means domain name *system* not *server*. So, are you asking you're not sure what DNS server has responded, or you don't know how to read the answers you got back from dig? Looking at your above dig results: Your command line asked whatever your computer's default DNS server was (configured in /etc/resolv.conf) to look up www.bbc.co.uk. The ANSWER section gives results about your query addresses. A query for www.bbc.co.uk gets a CNAME answer of www.bbc.net.uk (i.e. it says use that second name, instead). Followed by two answers for IPs for www.bbc.net.uk, saying to use either 212.58.246.93 or 212.58.246.92 (either will do). The QUERY TIME section says the server that answered was 192.168.1.1, so that would be the first DNS server address in your /etc/resolv.conf file. Second or third server addresses in that config file will only be consulted if the first one failed to respond, and there'd be a seriously long time-out period before that happened. Your router, at 192.168.1.1 may have tried to query 208.67.229.220:5353 and 208.67.222.222:5353 to find the results (I don't know if your router/modem can accept port numbers attached to the IPs, like that), and may have connected to them. Or, your ISP may have intercepted that. You might try using those IPs and ports with the dig command, directly. By default, dig will use your pre-configured DNS servers (in your /etc/resolv.conf file) unless you specify a server to query on its command line. That is *which* server to ask, not just what address you want to look up. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On Tue, 2013-11-12 at 23:09 +0800, Ed Greshko wrote: > If the ISP is doing transparent DNS proxy I seriously doubt that any > of that matters. It depends on how they're doing it. If they simply intercept port 53 traffic, then not using port 53 for your queries will bypass it. But if they also snoop on some other ports, or snoop on all traffic for things that look like DNS queries, then you're screwed. My opinion of ISPs that do transparent proxying, is rather low. I understand the point of view that some do that, so users don't have to configure their software. But my experience has been that ISPs do it to: Lower their operating costs, while still charging you the same, and to rake in more customers than their equipment (otherise) has bandwidth for. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 12/11/13 18:58, Cameron Simpson wrote: On 10Nov2013 20:18, Bob Goodwin wrote: [...] Further more their system does other things that I don't want to lose, namely the "free time" during the wee hours when I can allow the Apple computers to connect with iCloud, [...] Regarding reigning in the Apple stuff, what approach are you using here? Cheers, Most of the time I only allow connection to the iCloud, iTunes, etc. between midnight and five local time which is what they allow without tracking usage. I can open that if there is a need to connect at other times. I also have another filter that controls specific LAN addresses from connecting to the WAN except between midnight and five. And another that I hope blocks WAN traffic to my NFS also on the LAN. I use the Tomato 1.28 version of DD-WRT which permits a lot of control, logging, and I can view usage at any time even in real time which is a good way to see what my system download/upload speeds are as stuff is transferred. I also keep a daily record of the ISP'slogged data for my daily usage so I always know where I stand. I get 25 gigs per month but it costs me $10 a gig for anything I want beyond that. I've been managing our usage for about seven years now and it works well for me. Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11Nov2013 20:21, Bob Goodwin wrote: [...] > Source: > http://arstechnica.com/business/2012/01/how-viasats-exede-makes-satellite-broadband-not-suck/ > > He makes it sound that it's essential to stick with their software, > some parts of which are apparently contained in the modem. As I said > I am quite happy with the service, it normally works well and there > is nothing better available to me. [...] > If anyone understands what they are doing and can explain it to me I > am interested. If it is like the setup in our Gilat satellite modem here, there are two primary things going on. (Based on reading scattered stuff on the net when trying to debug an annoying problem some months ago.) The modem/satellite system does HTTP prefetching; when you fetch a web page the traffic is sniffed and requests for the page content (images etc) are prefetched. This step may happen upstream of the modem (eg in a proxy at the ISP) or it may happen in the modem - this is unclear; that "HTTP acceleration" is a modem-side setting suggests it may be happening in the modem. The other thing the Gilat modems do is "TCP acceleration". I gather a TCP connection is terminated localy at the modem, and the data stream sent with a more efficient protocol over the satellite section of the link and a TCP connection established on the upstream (far side of you->satellite->downstation) to carry the traffic from there to the target server. The TCP handshake takes place in real time - the modem does not falsely complete a connection only to have upstream fail, but past that the traffic is proxied. This may sound ineffectual, but in fact it has throughput benefits. The TCP connection from upstream to the target server can transfer data rapidly across the fast and low latency ground based network. The data beamed to/from the satellite is sent directly using the satellite specific data integrity protocols without the TCP packet tracking protocol, and the data from your host to the modem travels with low round trip latency to/from the modem I'm speaking here of the TCP packet ACK stuff, which is now you<->modem and upstream<->target-server. This results in greater throughput. Cheers, -- Cameron Simpson I took that Reading Dynamics course, and it really works. I read _War and Peace_ in an hour last night. It's about Russia. - W. Allen, ca. 1962 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/12/2013 04:03 PM, Cameron Simpson wrote: And the front line phone staff may be unaware of the issue. Speaking as somebody who did phone tech support for an ISP, that's quite possible. Granted, we did have a page that (supposedly) listed all known outages, but it was almost never up to date and usually just claimed that all was OK even when our email servers had been down for hours, or something like that. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 12Nov2013 13:19, Bob Goodwin wrote: > [...] I have had some intermittent problems recently but since > my complaint yesterday it has worked well. Coincidence perhaps? Maybe, maybe not. If one of their DNS servers was flakey, your complaint would not be alone. If they replaced/repaired their server, everyone will see the fix. And the front line phone staff may be unaware of the issue. -- Cameron Simpson I'm a man of my word. In the end, that's all there is. - Avon -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 10Nov2013 20:18, Bob Goodwin wrote: > [...] Further more their system > does other things that I don't want to lose, namely the "free time" > during the wee hours when I can allow the Apple computers to connect > with iCloud, [...] Regarding reigning in the Apple stuff, what approach are you using here? Cheers, -- Cameron Simpson A program in conformance will not tend to stay in conformance, because even if it doesn't change, the standard will. - Norman Diamond -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 12/11/13 13:28, Jim wrote: On 11/12/2013 01:19 PM, Bob Goodwin ~ Zuni, Virginia, USA wrote: On 12/11/13 13:03, Jim wrote: The DNS that is in your router is what IP it goes to, which in most cases your Internet Provider . Yes, normally you would expect that but Viasat Exede forces you to their DNS no matter what you set your router for and there is nothing wrong with the way that works as long as it is working normally. I have had some intermittent problems recently but since my complaint yesterday it has worked well. Coincidence perhaps? Bob The DNS numbers you have in /etc/resolv.conf would be the DNS-IP that it would goto. At least that is my understanding. It goes to the router, 192.168.1.1 and presently the router is set to use open.dns. [bobg@box10 ~]$ cat /etc/resolv.conf # Generated by NetworkManager nameserver 192.168.1.1 -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/12/2013 10:03 AM, Jim wrote: You can goto http://getip.com and it will tell you what your IP is. Hech it will even show you and everybody where you live. Actually, no. It won't. What it shows is where the DSLAM you're connected to is, and in my case, that's several miles away. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/12/2013 01:19 PM, Bob Goodwin ~ Zuni, Virginia, USA wrote: On 12/11/13 13:03, Jim wrote: The DNS that is in your router is what IP it goes to, which in most cases your Internet Provider . Yes, normally you would expect that but Viasat Exede forces you to their DNS no matter what you set your router for and there is nothing wrong with the way that works as long as it is working normally. I have had some intermittent problems recently but since my complaint yesterday it has worked well. Coincidence perhaps? Bob The DNS numbers you have in /etc/resolv.conf would be the DNS-IP that it would goto. At least that is my understanding. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 12/11/13 13:03, Jim wrote: The DNS that is in your router is what IP it goes to, which in most cases your Internet Provider . Yes, normally you would expect that but Viasat Exede forces you to their DNS no matter what you set your router for and there is nothing wrong with the way that works as long as it is working normally. I have had some intermittent problems recently but since my complaint yesterday it has worked well. Coincidence perhaps? Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/12/2013 12:00 PM, Bob Goodwin ~ Zuni, Virginia, USA wrote: On 12/11/13 09:41, Tim wrote: I get about a quarter or third of that time if I try other DNS servers. My own took 1500 mS the first time, then 6 ms for subsequent attempts (local cache is much quicker than internet propagation delays). Queries for other addresses took about 100 mS, so the BBC query must have been answered by something further away. My server checks it cache, then (if it doesn't have an answer) goes out to the root servers (to find out who would know the answer), then whatever servers the roots tell it, like a proper traditional DNS server. I consider 1.5 secs for a response to be unusually long. I couldn't put up with that, or worse, consistently. I changed the router configuration to use 208.67.229.220:5353 and 208.67.222.222:5353 and see the following: [root@box10 bobg]# dig www.bbc.co.uk ; <<>> DiG 9.9.3-rl.13207.22-P2-RedHat-9.9.3-5.P2.fc19 <<>> www.bbc.co.uk ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35870 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.bbc.co.uk.INA ;; ANSWER SECTION: www.bbc.co.uk.176INCNAMEwww.bbc.net.uk. www.bbc.net.uk.182INA212.58.246.93 www.bbc.net.uk.182INA212.58.246.92 ;; Query time: 616 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Tue Nov 12 11:46:20 EST 2013 ;; MSG SIZE rcvd: 100 As you say the cache is much faster, 2 ms as opposed to 616 ms. But I still don't know what DNS address it actually goes to, how do I find that? The DNS that is in your router is what IP it goes to, which in most cases your Internet Provider . In /etc/resolve.conf I put the Google DNS 8.8.8.8 and 8.8.0.0 and get better results. You can goto http://getip.com and it will tell you what your IP is. Hech it will even show you and everybody where you live. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 12/11/13 09:41, Tim wrote: I get about a quarter or third of that time if I try other DNS servers. My own took 1500 mS the first time, then 6 ms for subsequent attempts (local cache is much quicker than internet propagation delays). Queries for other addresses took about 100 mS, so the BBC query must have been answered by something further away. My server checks it cache, then (if it doesn't have an answer) goes out to the root servers (to find out who would know the answer), then whatever servers the roots tell it, like a proper traditional DNS server. I consider 1.5 secs for a response to be unusually long. I couldn't put up with that, or worse, consistently. I changed the router configuration to use 208.67.229.220:5353 and 208.67.222.222:5353 and see the following: [root@box10 bobg]# dig www.bbc.co.uk ; <<>> DiG 9.9.3-rl.13207.22-P2-RedHat-9.9.3-5.P2.fc19 <<>> www.bbc.co.uk ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35870 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.bbc.co.uk.INA ;; ANSWER SECTION: www.bbc.co.uk.176INCNAMEwww.bbc.net.uk. www.bbc.net.uk.182INA212.58.246.93 www.bbc.net.uk.182INA212.58.246.92 ;; Query time: 616 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Tue Nov 12 11:46:20 EST 2013 ;; MSG SIZE rcvd: 100 As you say the cache is much faster, 2 ms as opposed to 616 ms. But I still don't know what DNS address it actually goes to, how do I find that? -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/12/13 22:41, Tim wrote: > Next time it happens, start playing with the dig tool. Make queries > against your router, and against the DNS IPs the ISP provides (to the > router), and try some external DNS servers that have different ports > (the dig command lets you specify ports, read the man page, brief > outline below). Do queries for different addresses, if you keep > querying the same address, you'll just get results from a cache. If the ISP is doing transparent DNS proxy I seriously doubt that any of that matters. -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
Allegedly, on or about 11 November 2013, Bob Goodwin sent: > He makes it sound that it's essential to stick with their software, > some parts of which are apparently contained in the modem. As I said I > am quite happy with the service, it normally works well and there is > nothing better available to me. I also recently subscribed to their > voip service and find it superior to the cell phone [we discontinued > the land-line long ago] there is usually no detectable delay due to > transit time to the satellite. My only problem was the intermittent > DNS. Looking at that page, from what I can gather. They have a ground based network, with high speed and high bandwidth. It connects to you, other users, and probably other local services. The satellite is their link to things further away, and has latency by still high bandwidth, so things work well enough by the time that they've started and filled up a cache (e.g. watching streaming video). The modem has some custom compression to speed thing up even more - though any old BBS SysOp can tell you that you can only speed up still-compressible data, that way, not all data. So, again, I say just find yourself a decent DNS server, and use it instead. You'll still be going through their caches and proxies for the data, you'll just be getting the addresses quicker. Next time it happens, start playing with the dig tool. Make queries against your router, and against the DNS IPs the ISP provides (to the router), and try some external DNS servers that have different ports (the dig command lets you specify ports, read the man page, brief outline below). Do queries for different addresses, if you keep querying the same address, you'll just get results from a cache. dig @server -p number address Substituting "server" for the address of server you're going to query, "number" for the port number you're querying through (if not the usual port 53), and address for the address you want to query. Have you tried OpenDNS on port 5353 instead of port 53? If you're lucky, your ISP is only doing a simplistic buggery of DNS on 53. e.g. dig @208.67.222.222 -p 5353 www.bbc.co.uk ; <<>> DiG 9.9.3-rl.156.01-P1-RedHat-9.9.3-3.P1.fc17 <<>> @208.67.222.222 -p 5353 www.bbc.co.uk ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61634 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.bbc.co.uk. IN A ;; ANSWER SECTION: www.bbc.co.uk. 291 IN CNAME www.bbc.net.uk. www.bbc.net.uk. 165 IN A 212.58.244.68 www.bbc.net.uk. 165 IN A 212.58.244.69 ;; Query time: 98 msec ;; SERVER: 208.67.222.222#5353(208.67.222.222) ;; WHEN: Wed Nov 13 01:03:31 CST 2013 ;; MSG SIZE rcvd: 100 I get about a quarter or third of that time if I try other DNS servers. My own took 1500 mS the first time, then 6 ms for subsequent attempts (local cache is much quicker than internet propagation delays). Queries for other addresses took about 100 mS, so the BBC query must have been answered by something further away. My server checks it cache, then (if it doesn't have an answer) goes out to the root servers (to find out who would know the answer), then whatever servers the roots tell it, like a proper traditional DNS server. I consider 1.5 secs for a response to be unusually long. I couldn't put up with that, or worse, consistently. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On Sun, Nov 10, 2013 at 5:41 PM, Bob Goodwin ~ Zuni, Virginia, USA wrote: > On 10/11/13 19:28, Sam Varshavchik wrote: >> Bob Goodwin ~ Zuni, Virginia, USA writes: >>> No, it won't allow any other DNS server, no matter what I configure it >>> for it always goes to theirs, that's why I gave up open.dns. This was a >>> change >> >> DD-WRT does not give you the option to use fixed DNS servers, instead of >> whatever DHCP servers it gets via DHCP from your ISP? >> >> I'm surprised to hear that. Or, rereading what you earlier wrote, maybe >> you're saying that your ISP blocks port 53 traffic, and will only let you >> use their DNS servers. > > DD-WRT will let me use any DNS I want, it's Viasat's system that changes it. > They do some sort of caching to reduce traffic through the satellite > apparently ... Initially I had it configured for open.dns but it wasn't long > before I found it wasn't going there. Wild guess: maybe the DNS information you have manually provided to DD-WRT got made wrong by changes in the network (seems plausible given the IP lookup data others have given), and something's going wrong with the magic they use to override other DNS servers besides theirs (including the one you're using which you thought was valid but perhaps has now changed). Try reconfiguring DD-WRT to get its DNS information from your ISP's DHCP server and see if your problem persists. (I believe you just set Static DNS to all 0s in DD-WRT to accomplish this.) -T.C. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/11/13 19:12, Tim wrote: That'd be HTTP caching. They don't need to subvert DNS records for you to see cached websites. Unless they're doing something stupid, your web requests are still made of the original IPs, just the results are cached. I have the same thing, here, on my LAN. A Squid proxy server, so that if I have guests doing the "look at this" thing amongst themselves, or a bunch of Windows PCs doing updates, everyone after the first query sees the cached version. You can try it out, and see. Find a public DNS server that you can access on a different-than-usual port. Make a rule on your gateway that connection attempts to your router IP and DNS port get redirected to the external DNS server on the unusual port. It's probably possible to make an outgoing redirection rule on the PC that your testing, itself. As far as them optimising things, with satellite internet, there's a prolonged propagation delay. So them doing local caching means that you get to see cached data on this side of the satellite, rather than have to wait for it to come through it. Years ago I used an ISP that did that sort of thing, their service was dreadful. Everything was late, worse than dial-up. Their crap performance was the thing that pushed me into running my own DNS servers. Their DNS servers were even worse than their everything else that they did. Frequently, it could take half a minute for it to return a result. When you consider that way too many pages are a construct of data from here, there, and everywhere, not just the sites own service, it could take an age to load a page. Any service that mucks you about, and fobs you off, and leaves you trying to resolve a problem for days on end, doesn't deserve your custom. Especially if the problem is theirs. As I said I don't know exactly what they are doing but I do know that I'm not smart enough to work around it. I spent quite a bit of effort Googling "Viasat Exede" and it seems there's a dearth of information other than sales hype. Here's an excerpt from a interview I did find, still not very informative: "The teleports are associated regionally with customers, so there's no dynamic routing being done by the satellite. "If we did routing in the satellite, we'd be getting about 10 gigabits of throughput," Dankberg said. "With bridging, we get more than 10 times that." Just for scale, 140 gigabits per second is 20 times the bandwidth capability of the previously existing WildBlue satellite service. "The two largest satellite operators have about a hundred satellites," Dankberg said, "and between them they have the same bandwidth as this one satellite."That sort of capacity, he says, alters the economics of satellite broadband. There are some things bandwidth can't overcome, and one of them is the laws of physics. Satellite is still prone to latency, which means it's not the best choice for applications that need a short time-of-flight—like online gaming, for example (unless you're a big fan of lag). "We tell people up front if they're looking for a gaming connection, this isn't it," Dankberg conceded. There's also a small, but noticeable delay on voice-over-IP phone calls over Exede, but not any more than a typical wireless call. I placed a call over a VoIP phone tethered to an Exede home unit, and the conversation was better than cellular quality." Source: http://arstechnica.com/business/2012/01/how-viasats-exede-makes-satellite-broadband-not-suck/ He makes it sound that it's essential to stick with their software, some parts of which are apparently contained in the modem. As I said I am quite happy with the service, it normally works well and there is nothing better available to me. I also recently subscribed to their voip service and find it superior to the cell phone [we discontinued the land-line long ago] there is usually no detectable delay due to transit time to the satellite. My only problem was the intermittent DNS. It has not failed today that I am aware of. The kids are not happy due to it's inability to handle on-line gaming with their brother in Chicago. That is not a requirement in my book. If anyone understands what they are doing and can explain it to me I am interested. Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
Tim: >> Unless you're doing something odd, the amount of traffic from DNS >> data is minuscule compared to everything else. Bob Goodwin: > But what if they are caching stuff, e.g. foxnews, some popular video > clips, etc. and delivering them to the user without going through the > satellite loop? I don't know what they are doing but they claim to be > "optimizing" the system with their caching. That'd be HTTP caching. They don't need to subvert DNS records for you to see cached websites. Unless they're doing something stupid, your web requests are still made of the original IPs, just the results are cached. I have the same thing, here, on my LAN. A Squid proxy server, so that if I have guests doing the "look at this" thing amongst themselves, or a bunch of Windows PCs doing updates, everyone after the first query sees the cached version. You can try it out, and see. Find a public DNS server that you can access on a different-than-usual port. Make a rule on your gateway that connection attempts to your router IP and DNS port get redirected to the external DNS server on the unusual port. It's probably possible to make an outgoing redirection rule on the PC that your testing, itself. As far as them optimising things, with satellite internet, there's a prolonged propagation delay. So them doing local caching means that you get to see cached data on this side of the satellite, rather than have to wait for it to come through it. Years ago I used an ISP that did that sort of thing, their service was dreadful. Everything was late, worse than dial-up. Their crap performance was the thing that pushed me into running my own DNS servers. Their DNS servers were even worse than their everything else that they did. Frequently, it could take half a minute for it to return a result. When you consider that way too many pages are a construct of data from here, there, and everywhere, not just the sites own service, it could take an age to load a page. Any service that mucks you about, and fobs you off, and leaves you trying to resolve a problem for days on end, doesn't deserve your custom. Especially if the problem is theirs. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/11/13 08:40, Sam Varshavchik wrote: Don't exclude the possibility that the modem itself is flipping out. My DSL started going down once a week or so, some years ago. Powercycling the modem always put me back online. Troubleshooting with the ISP wasn't very productive. I ended up buying a new modem, and that was it. The old modem is still sitting in a dusty cabinet, and I actually pulled it out, in a pinch, when I suspected a problem with my current modem. I would not hesitate to try a new one if it was readily available to me but as I understandit the modem is unique to their service/system. The old one had transmit and receive coax cables between it and the antenna, this one uses only one coax but I believe part of the radio circuitry is in the modem with intermediate frequency signaling between it and the antenna. It needs to do things like control the subscriber transmitter power with varying weather conditions, stuff that would be different than a cable modem. Tech support did suggest that it could be a modem problem but I generally try to avoid going through their troubleshooting procedure, at least leave that 'til last.. -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
Bob Goodwin ~ Zuni, Virginia, USA writes: But what if they are caching stuff, e.g. foxnews, some popular video clips, etc. and delivering them to the user without going through the satellite loop? I don't know what they are doing but they claim to be "optimizing" the system with their caching. I'm not concerned about the trivial usage attributable to DNS. I just want it to work. As it has been I've had to restart the Viasat modem several times a week, an annoyance I will have to put up with it seems, my experience has been that such things eventually change, hopefully for the better. Don't exclude the possibility that the modem itself is flipping out. My DSL started going down once a week or so, some years ago. Powercycling the modem always put me back online. Troubleshooting with the ISP wasn't very productive. I ended up buying a new modem, and that was it. The old modem is still sitting in a dusty cabinet, and I actually pulled it out, in a pinch, when I suspected a problem with my current modem. pgpr0WqzBsYmf.pgp Description: PGP signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/11/13 07:18, Tim wrote: Allegedly, on or about 10 November 2013, Bob Goodwin ~ Zuni, Virginia, USA sent: when I began using this service I was advised not to try to work around their system since it would result in my being charged for higher usage and my allotment is limited. Unless you're doing something odd, the amount of traffic from DNS data is minuscule compared to everything else. But what if they are caching stuff, e.g. foxnews, some popular video clips, etc. and delivering them to the user without going through the satellite loop? I don't know what they are doing but they claim to be "optimizing" the system with their caching. I'm not concerned about the trivial usage attributable to DNS. I just want it to work. As it has been I've had to restart the Viasat modem several times a week, an annoyance I will have to put up with it seems, my experience has been that such things eventually change, hopefully for the better. -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
Allegedly, on or about 10 November 2013, Bob Goodwin ~ Zuni, Virginia, USA sent: > when I began using this service I was advised not to try to work > around their system since it would result in my being charged for > higher usage and my allotment is limited. Unless you're doing something odd, the amount of traffic from DNS data is minuscule compared to everything else. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 10/11/13 19:54, Tim wrote: There is a chance that you could still use an outside DNS service, if you can access one that uses a different port than your ISP is intercepting. This would, also, depend on you either making up TCP/IP redirection rules on your gateway so your clients queries go to that unusual port. Or, running your own DNS server on a PC. You'd configure your clients to use that DNS server as a normal DNS server, and you'd configure the DNS server to do the unusual port queries. ISPs are notorious for having awful DNS services, particularly ones that play silly games with forcing you to use them. So running your own DNS server, that's totally under your control, can be quite advantageous. The mini DNS servers in some modem/routers are awful, and have no configuration options. Some modem/routers don't have a DNS server, they simply act as a proxy between you and the ISP supplied DNS server IPs. Yes,when I began using this service I was advised not to try to work around their system since it would result in my being charged for higher usage and my allotment is limited. Further more their system does other things that I don't want to lose, namely the "free time" during the wee hours when I can allow the Apple computers to connect with iCloud, etc. DD-WRT is configured to deal with thatand as I say it all works except for this intermittent loss of DNS that has cropped up recently. Normally the system works well, I don't want to change it, I just need to convince them there is a DNS problem and I think it is in their system. This thread has provided some help in how to do that. -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 10/11/13 19:53, Sam Varshavchik wrote: I need to convince them they have a problem, will check more next time it goes out. Get someone on the horn who has a minimum of an understanding, and tell them you can't ping their DNS servers. Yes, I intend to do that, thought I had enough information this morning but the tech support person took offense at being told their DNS was failing and began telling me some bazaar things, she was confusing mac addresses with URLs, wanted to test my NIC. I explained that the trouble was with two Linux computers and several Apple Mac devices. I was getting no where ... :-( I will try again when the problem reoccurs. -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
Allegedly, on or about 10 November 2013, Bob Goodwin ~ Zuni, Virginia, USA sent: > I used to subscribe to open.dns but with this satellite system it no > longer functions and we are required to use their dns which is part of > some optimization system Viasat uses. There is a chance that you could still use an outside DNS service, if you can access one that uses a different port than your ISP is intercepting. This would, also, depend on you either making up TCP/IP redirection rules on your gateway so your clients queries go to that unusual port. Or, running your own DNS server on a PC. You'd configure your clients to use that DNS server as a normal DNS server, and you'd configure the DNS server to do the unusual port queries. ISPs are notorious for having awful DNS services, particularly ones that play silly games with forcing you to use them. So running your own DNS server, that's totally under your control, can be quite advantageous. The mini DNS servers in some modem/routers are awful, and have no configuration options. Some modem/routers don't have a DNS server, they simply act as a proxy between you and the ISP supplied DNS server IPs. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
Bob Goodwin ~ Zuni, Virginia, USA writes: On 10/11/13 19:12, Steven Stern wrote: Use 8.8.8.8 and 8.8.4.4 (Google Public DNS Servers) or 208.67.222.222 and 208.67.220.220 (OpenDNS) The problem is probably with your ISP's DNS servers. Yes, those worked well when I was able to use them, this system goes to it's own DNS no matter what I ask it, and the DNS they provide works well most of the time, it's just that recently I have been seeing it fail and fixing it requires rebooting the Viasat modem. I need to convince them they have a problem, will check more next time it goes out. Get someone on the horn who has a minimum of an understanding, and tell them you can't ping their DNS servers. pgp7QF2POCK4t.pgp Description: PGP signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
Bob Goodwin ~ Zuni, Virginia, USA writes: On 10/11/13 19:28, Sam Varshavchik wrote: Bob Goodwin ~ Zuni, Virginia, USA writes: No, it won't allow any other DNS server, no matter what I configure it for it always goes to theirs, that's why I gave up open.dns. This was a change DD-WRT does not give you the option to use fixed DNS servers, instead of whatever DHCP servers it gets via DHCP from your ISP? I'm surprised to hear that. Or, rereading what you earlier wrote, maybe you're saying that your ISP blocks port 53 traffic, and will only let you use their DNS servers. DD-WRT will let me use any DNS I want, it's Viasat's system that changes it. They do some sort of caching to reduce traffic through the satellite apparently ... Initially I had it configured for open.dns but it wasn't long before I found it wasn't going there. The only option I can think of is to use an SSL-based VPN tunnel, to a friendly VPS provider. Of course, this is going to kill your bandwidth. pgpA6hKUhK2XM.pgp Description: PGP signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
Allegedly, on or about 10 November 2013, Bob Goodwin ~ Zuni, Virginia, USA sent: > Am I missing some point here? Is there some connection between dhcp > and dns that I am not aware of. My dhcp server is in the router and > deals with about thirty addresses on the LAN and works faultlessly as > far as I can see. (Almost) only as far as making sure that your DHCP server tells its clients the right IP to use for their DNS queries. Which it looks like it is, from subsequent replies. DCHP servers tell the clients various things to configure their network, one of which is what DNS server IPs to use. Others are the clients own IP, and things like the gateway (where the clients connect through to the outside world), netmask (which sets the boundary between what's inside or outside). So, if your clients have proper networking addresses, you can ignore debugging your DHCP server configuration. If they have some details wrong, then you need to check whether your DHCP server is doling out the right information, or your clients are ignoring it (some people set manual overriding configurations on their PCs). -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 10/11/13 19:28, Sam Varshavchik wrote: Bob Goodwin ~ Zuni, Virginia, USA writes: No, it won't allow any other DNS server, no matter what I configure it for it always goes to theirs, that's why I gave up open.dns. This was a change DD-WRT does not give you the option to use fixed DNS servers, instead of whatever DHCP servers it gets via DHCP from your ISP? I'm surprised to hear that. Or, rereading what you earlier wrote, maybe you're saying that your ISP blocks port 53 traffic, and will only let you use their DNS servers. DD-WRT will let me use any DNS I want, it's Viasat's system that changes it. They do some sort of caching to reduce traffic through the satellite apparently ... Initially I had it configured for open.dns but it wasn't long before I found it wasn't going there. -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 10/11/13 18:24, Ed Greshko wrote: Quite some time ago it was determined that your ISP uses "transparent DNS proxy" to force you to use their DNS servers. But, I really would ask them about their use of IP addresses as this is the output of whois 182.63.128.68 inetnum:182.62.0.0 - 182.63.255.255 netname:DIGI-MY descr: DiGi Telecommunications Sdn Bhd descr: Lot 10, Jalan Delima 1/1, Subang Hi-Tech Industrial Park, descr: 4 Shah Alam, Selangor Darul Ehsan, Malaysia country:MY admin-c:DIA1-AP tech-c: DI39-AP mnt-by: APNIC-HM mnt-lower: MAINT-MY-DIGI-SB mnt-routes: MAINT-MY-DIGI-SB status: ALLOCATED PORTABLE remarks:-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+ remarks:This object can only be updated by APNIC hostmasters. remarks:To update this object, please contact APNIC remarks:hostmasters and include your organisation's account remarks:name in the subject line. remarks:-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+ mnt-irt:IRT-DIGI-MY changed:hm-chan...@apnic.net 20100224 source: APNIC One wonders if their screwing with IP addresses doesn't fail at times. Maybe, sometimes, they actually transmit the DNS request to Malaysia. I would ask the ISP what the IP address of their DNS servers should be. I don't remember how I got those DNS addresses but they have been working for a couple of years without a problem until recently. I will look into it some more tomorrow. -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 10/11/13 19:12, Steven Stern wrote: Use 8.8.8.8 and 8.8.4.4 (Google Public DNS Servers) or 208.67.222.222 and 208.67.220.220 (OpenDNS) The problem is probably with your ISP's DNS servers. Yes, those worked well when I was able to use them, this system goes to it's own DNS no matter what I ask it, and the DNS they provide works well most of the time, it's just that recently I have been seeing it fail and fixing it requires rebooting the Viasat modem. I need to convince them they have a problem, will check more next time it goes out. -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
Bob Goodwin ~ Zuni, Virginia, USA writes: No, it won't allow any other DNS server, no matter what I configure it for it always goes to theirs, that's why I gave up open.dns. This was a change DD-WRT does not give you the option to use fixed DNS servers, instead of whatever DHCP servers it gets via DHCP from your ISP? I'm surprised to hear that. Or, rereading what you earlier wrote, maybe you're saying that your ISP blocks port 53 traffic, and will only let you use their DNS servers. pgpyfU8mfGSpa.pgp Description: PGP signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/10/2013 02:29 PM, Bob Goodwin ~ Zuni, Virginia, USA wrote: > DD-WRT configuration is set for the following: > > 182.63.128.68 and 182.63.128.69 Use 8.8.8.8 and 8.8.4.4 (Google Public DNS Servers) or 208.67.222.222 and 208.67.220.220 (OpenDNS) The problem is probably with your ISP's DNS servers. -- -- Steve -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/11/13 06:32, Bob Goodwin ~ Zuni, Virginia, USA wrote: > No, it won't allow any other DNS server, no matter what I configure it for it > always goes to theirs, that's why I gave up open.dns. This was a change when > they began to offer this high speed service, before that I always used some > other DNS server. > > [bobg@box10 ~]$ dig google.com @182.63.128.68 > > ; <<>> DiG 9.9.3-rl.13207.22-P2-RedHat-9.9.3-5.P2.fc19 <<>> google.com > @182.63.128.68 > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61788 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;google.com.INA > > ;; ANSWER SECTION: > google.com.1INA74.125.224.206 > google.com.1INA74.125.224.192 > google.com.1INA74.125.224.193 > google.com.1INA74.125.224.194 > google.com.1INA74.125.224.195 > google.com.1INA74.125.224.196 > google.com.1INA74.125.224.197 > google.com.1INA74.125.224.198 > google.com.1INA74.125.224.199 > google.com.1INA74.125.224.200 > google.com.1INA74.125.224.201 > > ;; Query time: 5 msec > ;; SERVER: 182.63.128.68#53(182.63.128.68) > ;; WHEN: Sun Nov 10 17:28:41 EST 2013 > ;; MSG SIZE rcvd: 204 > > > I'll try dig next time it goes out. I should have done that this morning when > it went down. > > Thanks for the help. Quite some time ago it was determined that your ISP uses "transparent DNS proxy" to force you to use their DNS servers. But, I really would ask them about their use of IP addresses as this is the output of whois 182.63.128.68 inetnum:182.62.0.0 - 182.63.255.255 netname:DIGI-MY descr: DiGi Telecommunications Sdn Bhd descr: Lot 10, Jalan Delima 1/1, Subang Hi-Tech Industrial Park, descr: 4 Shah Alam, Selangor Darul Ehsan, Malaysia country:MY admin-c:DIA1-AP tech-c: DI39-AP mnt-by: APNIC-HM mnt-lower: MAINT-MY-DIGI-SB mnt-routes: MAINT-MY-DIGI-SB status: ALLOCATED PORTABLE remarks:-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+ remarks:This object can only be updated by APNIC hostmasters. remarks:To update this object, please contact APNIC remarks:hostmasters and include your organisation's account remarks:name in the subject line. remarks:-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+ mnt-irt:IRT-DIGI-MY changed:hm-chan...@apnic.net 20100224 source: APNIC One wonders if their screwing with IP addresses doesn't fail at times. Maybe, sometimes, they actually transmit the DNS request to Malaysia. I would ask the ISP what the IP address of their DNS servers should be. -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 10/11/13 16:38, staticsafe wrote: DD-WRT configuration is set for the following: > >182.63.128.68 and 182.63.128.69 > >Normally it works well and does its job instantly as far as I can tell. > dresden ~ # dig google.com @182.63.128.68 ; <<>> DiG 9.9.3-P2 <<>> google.com @182.63.128.68 ;; global options: +cmd ;; connection timed out; no servers could be reached dresden ~ # dig google.com @182.63.128.69 ; <<>> DiG 9.9.3-P2 <<>> google.com @182.63.128.69 ;; global options: +cmd ;; connection timed out; no servers could be reached That might be your problem, I would suggest testing yourself to see if they are down for you as well. As a temporary measure you can use Google Public DNS: https://developers.google.com/speed/public-dns/ No, it won't allow any other DNS server, no matter what I configure it for it always goes to theirs, that's why I gave up open.dns. This was a change when they began to offer this high speed service, before that I always used some other DNS server. [bobg@box10 ~]$ dig google.com @182.63.128.68 ; <<>> DiG 9.9.3-rl.13207.22-P2-RedHat-9.9.3-5.P2.fc19 <<>> google.com @182.63.128.68 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61788 ;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;google.com.INA ;; ANSWER SECTION: google.com.1INA74.125.224.206 google.com.1INA74.125.224.192 google.com.1INA74.125.224.193 google.com.1INA74.125.224.194 google.com.1INA74.125.224.195 google.com.1INA74.125.224.196 google.com.1INA74.125.224.197 google.com.1INA74.125.224.198 google.com.1INA74.125.224.199 google.com.1INA74.125.224.200 google.com.1INA74.125.224.201 ;; Query time: 5 msec ;; SERVER: 182.63.128.68#53(182.63.128.68) ;; WHEN: Sun Nov 10 17:28:41 EST 2013 ;; MSG SIZE rcvd: 204 I'll try dig next time it goes out. I should have done that this morning when it went down. Thanks for the help. Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/11/13 05:38, staticsafe wrote: > On 11/10/2013 15:29, Bob Goodwin ~ Zuni, Virginia, USA wrote: >> I used to subscribe to open.dns but with this satellite system it no >> longer functions and we are required to use their dns which is part of >> some optimization system Viasat uses. >> >> DD-WRT configuration is set for the following: >> >> 182.63.128.68 and 182.63.128.69 >> >> Normally it works well and does its job instantly as far as I can tell. >> > dresden ~ # dig google.com @182.63.128.68 > > ; <<>> DiG 9.9.3-P2 <<>> google.com @182.63.128.68 > ;; global options: +cmd > ;; connection timed out; no servers could be reached > > dresden ~ # dig google.com @182.63.128.69 > > ; <<>> DiG 9.9.3-P2 <<>> google.com @182.63.128.69 > ;; global options: +cmd > ;; connection timed out; no servers could be reached > > That might be your problem, I would suggest testing yourself to see if > they are down for you as well. > > As a temporary measure you can use Google Public DNS: > https://developers.google.com/speed/public-dns/ whois shows those IP's belonging to DiGi Telecommunications Sdn Bhd in Malaysia. -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/10/2013 15:29, Bob Goodwin ~ Zuni, Virginia, USA wrote: > > I used to subscribe to open.dns but with this satellite system it no > longer functions and we are required to use their dns which is part of > some optimization system Viasat uses. > > DD-WRT configuration is set for the following: > > 182.63.128.68 and 182.63.128.69 > > Normally it works well and does its job instantly as far as I can tell. > dresden ~ # dig google.com @182.63.128.68 ; <<>> DiG 9.9.3-P2 <<>> google.com @182.63.128.68 ;; global options: +cmd ;; connection timed out; no servers could be reached dresden ~ # dig google.com @182.63.128.69 ; <<>> DiG 9.9.3-P2 <<>> google.com @182.63.128.69 ;; global options: +cmd ;; connection timed out; no servers could be reached That might be your problem, I would suggest testing yourself to see if they are down for you as well. As a temporary measure you can use Google Public DNS: https://developers.google.com/speed/public-dns/ -- staticsafe O< ascii ribbon campaign - stop html mail - www.asciiribbon.org Please don't top post. It is not logical. Please don't CC me! I'm subscribed to whatever list I just posted on. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 10/11/13 15:19, staticsafe wrote: On 11/10/2013 15:17, Bob Goodwin ~ Zuni, Virginia, USA wrote: Well this is what I see: [bobg@box10 ~]$ cat /etc/resolv.conf # Generated by NetworkManager nameserver 192.168.1.1 192.168.1.1 is my Linksys E3000 DD-WRT router. DD-WRT usually runs a forwarder, check your router to see where it is forwarding DNS queries. I used to subscribe to open.dns but with this satellite system it no longer functions and we are required to use their dns which is part of some optimization system Viasat uses. DD-WRT configuration is set for the following: 182.63.128.68 and 182.63.128.69 Normally it works well and does its job instantly as far as I can tell. -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/10/2013 15:17, Bob Goodwin ~ Zuni, Virginia, USA wrote: > Well this is what I see: > > [bobg@box10 ~]$ cat /etc/resolv.conf > # Generated by NetworkManager > nameserver 192.168.1.1 > > > 192.168.1.1 is my Linksys E3000 DD-WRT router. > DD-WRT usually runs a forwarder, check your router to see where it is forwarding DNS queries. -- staticsafe O< ascii ribbon campaign - stop html mail - www.asciiribbon.org Please don't top post. It is not logical. Please don't CC me! I'm subscribed to whatever list I just posted on. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 10/11/13 15:10, staticsafe wrote: On 11/10/2013 14:57, Bob Goodwin ~ Zuni, Virginia, USA wrote: Recently we have begun to have problems with our browsers stopping to work, ask it to go to a bookmark address and nothing happens, everything stops until an error message comes up that the address can not be found. Thunderbird continues to receive e-mail unless I restart Thunderbird, then it is unable to find gmail.com. The problem exists on two F-19 computers and several Apple computers on the LAN, in fact I often become aware of the problem when someone complains that the internet connection is down. I can always restore normal operation by re-starting the Viasat modem, a process that takes several minutes and is an annoyance. I have determined that I can enter a numeric address e.g. 199.106.52.212 for viasat.com and that works as expected. At the request of viasat tech support I tried taking the router out of the circuit and connecting directly to the modem, that effected no change. Curiously, at the time this this morning when the problem was manifest tech support's "computer was down" which left me wondering if there was a correlation with my apparent DNS problem. I was asked to call back in a few hours, I did that. The tech support person seemed to take offense at my claiming there was a DNS problem and went on to explain that I probably have a dhcp problem and we need to start by "re-setting my NIC." From there on the conversation began to deteriorate and she accused me of shouting at her, I was able to extricate myself gracefully after that and agree that I would call back when I had more time to devote to troubleshooting. Am I missing some point here? Is there some connection between dhcp and dns that I am not aware of. My dhcp server is in the router and deals with about thirty addresses on the LAN and works faultlessly as far as I can see. Any thoughts appreciated, Bob DHCP is used to distribute DNS resolvers to your LAN. What resolvers do you get via DHCP? (Check Network Manager or /etc/resolv.conf) Well this is what I see: [bobg@box10 ~]$ cat /etc/resolv.conf # Generated by NetworkManager nameserver 192.168.1.1 192.168.1.1 is my Linksys E3000 DD-WRT router. -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS problem -
On 11/10/2013 14:57, Bob Goodwin ~ Zuni, Virginia, USA wrote: > > Recently we have begun to have problems with our browsers stopping to > work, ask it to go to a bookmark address and nothing happens, everything > stops until an error message comes up that the address can not be found. > > Thunderbird continues to receive e-mail unless I restart Thunderbird, > then it is unable to find gmail.com. The problem exists on two F-19 > computers and several Apple computers on the LAN, in fact I often become > aware of the problem when someone complains that the internet connection > is down. > > I can always restore normal operation by re-starting the Viasat modem, a > process that takes several minutes and is an annoyance. > > I have determined that I can enter a numeric address e.g. 199.106.52.212 > for viasat.com and that works as expected. At the request of viasat tech > support I tried taking the router out of the circuit and connecting > directly to the modem, that effected no change. Curiously, at the time > this this morning when the problem was manifest tech support's "computer > was down" which left me wondering if there was a correlation with my > apparent DNS problem. I was asked to call back in a few hours, I did that. > > The tech support person seemed to take offense at my claiming there was > a DNS problem and went on to explain that I probably have a dhcp problem > and we need to start by "re-setting my NIC." From there on the > conversation began to deteriorate and she accused me of shouting at her, > I was able to extricate myself gracefully after that and agree that I > would call back when I had more time to devote to troubleshooting. > > Am I missing some point here? Is there some connection between dhcp and > dns that I am not aware of. My dhcp server is in the router and deals > with about thirty addresses on the LAN and works faultlessly as far as I > can see. > > Any thoughts appreciated, > > Bob > > DHCP is used to distribute DNS resolvers to your LAN. What resolvers do you get via DHCP? (Check Network Manager or /etc/resolv.conf) -- staticsafe O< ascii ribbon campaign - stop html mail - www.asciiribbon.org Please don't top post. It is not logical. Please don't CC me! I'm subscribed to whatever list I just posted on. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
DNS problem -
Recently we have begun to have problems with our browsers stopping to work, ask it to go to a bookmark address and nothing happens, everything stops until an error message comes up that the address can not be found. Thunderbird continues to receive e-mail unless I restart Thunderbird, then it is unable to find gmail.com. The problem exists on two F-19 computers and several Apple computers on the LAN, in fact I often become aware of the problem when someone complains that the internet connection is down. I can always restore normal operation by re-starting the Viasat modem, a process that takes several minutes and is an annoyance. I have determined that I can enter a numeric address e.g. 199.106.52.212 for viasat.com and that works as expected. At the request of viasat tech support I tried taking the router out of the circuit and connecting directly to the modem, that effected no change. Curiously, at the time this this morning when the problem was manifest tech support's "computer was down" which left me wondering if there was a correlation with my apparent DNS problem. I was asked to call back in a few hours, I did that. The tech support person seemed to take offense at my claiming there was a DNS problem and went on to explain that I probably have a dhcp problem and we need to start by "re-setting my NIC." From there on the conversation began to deteriorate and she accused me of shouting at her, I was able to extricate myself gracefully after that and agree that I would call back when I had more time to devote to troubleshooting. Am I missing some point here? Is there some connection between dhcp and dns that I am not aware of. My dhcp server is in the router and deals with about thirty addresses on the LAN and works faultlessly as far as I can see. Any thoughts appreciated, Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-19/64 bit Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: DNS Problem Maintaining Domain on Fedora VM
On Thu, 2011-06-23 at 07:06 -0400, Tod Thomas wrote: > I have a FC14 VM running on a Win7 box using Virtual Box. I cannot get > Network Manager to keep the domain name so I'm constantly having to add > it at the end of my host names which is a little annoying. I've googled > around and there are a number of suggestions but none of them are > definitive. Is there a single solution I can use in Network Manager > that I'm just not trying? Well, generally, the DNS suffix is determined by doing a reverse DNS lookup on your IP, and supplying on in the configuration is only needed when that cannot be done (i.e. because you have broken DNS - which could mean no DNS server providing the answer, or you want to provide a different answer). So, perhaps it's a different problem that you need to fix: DNS, itself (making suitable entries in the hosts file, or records in the DNS server, or specifying a DNS server that can answer the query). Or, the DHCP server configuration (making sure the right domain name is supplied to the client). That is how NetworkManager will be adding what it thinks is the hostname to the resolv.conf file (via reverse-DNS lookups or DHCP-supplied data). -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: DNS Problem Maintaining Domain on Fedora VM
On 06/23/2011 07:56 AM, Tom Horsley wrote: > On Thu, 23 Jun 2011 07:06:55 -0400 > Tod Thomas wrote: > >> I cannot get >> Network Manager to keep the domain name so I'm constantly having to add >> it at the end of my host names which is a little annoying. > In theory you can make NM stop fooling with the resolv.conf > file by putting PEERDNS="no" in the /etc/sysconfig/network-scripts/ifcfg-* > file. Then you can just manually edit resolv.conf to have > the correct search path (after rebooting to make sure all the > resolv.conf editing is really finished). > > The other "big hammer" approach which I have had to use on > some machines is to edit /etc/resolv.conf manually, then > do "chattr +i /etc/resolv.conf" - that makes the file > "immutable" and even root can't write on it anymore. I'm already using PEERDNS="no". I'm afraid if I try the immutable trick I'll cause DHCP problems when VPN'ing. Is that a reasonable concern? Any other options? I noticed a PEERDNS="no" bug reported under fc13 but it looks like it lapsed due to fc13's EOL. - Tod -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: DNS Problem Maintaining Domain on Fedora VM
On Thu, 23 Jun 2011 07:06:55 -0400 Tod Thomas wrote: > I cannot get > Network Manager to keep the domain name so I'm constantly having to add > it at the end of my host names which is a little annoying. In theory you can make NM stop fooling with the resolv.conf file by putting PEERDNS="no" in the /etc/sysconfig/network-scripts/ifcfg-* file. Then you can just manually edit resolv.conf to have the correct search path (after rebooting to make sure all the resolv.conf editing is really finished). The other "big hammer" approach which I have had to use on some machines is to edit /etc/resolv.conf manually, then do "chattr +i /etc/resolv.conf" - that makes the file "immutable" and even root can't write on it anymore. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: DNS Problem Maintaining Domain on Fedora VM
Am 23.06.2011 13:06, schrieb Tod Thomas: > I have a FC14 VM running on a Win7 box using Virtual Box. I cannot get > Network Manager to keep the domain name so I'm constantly having to add > it at the end of my host names which is a little annoying. I've googled > around and there are a number of suggestions but none of them are > definitive. Is there a single solution I can use in Network Manager > that I'm just not trying? i do not use networknanager but google for "dns suffix" using only the classical network-service works like below [root@srv-rhsoft:~]$ cat /etc/resolv.conf nameserver 127.0.0.1 domain rhsoft.net search rhsoft.net thelounge.net vmware.local test.rh signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
DNS Problem Maintaining Domain on Fedora VM
I have a FC14 VM running on a Win7 box using Virtual Box. I cannot get Network Manager to keep the domain name so I'm constantly having to add it at the end of my host names which is a little annoying. I've googled around and there are a number of suggestions but none of them are definitive. Is there a single solution I can use in Network Manager that I'm just not trying? Thanks - Tod -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: another DNS problem
ma, 2010-11-01 kello 01:54 +1030, Tim kirjoitti: > Well, the error message said "temporary" failure, with a "deferred" > status of the queue. Once the problem goes away, it can retry. Or may > just keep retrying, anyway. > > The obvious question occurs: Had you restarted the mailserver during > these tests? You usually have to restart servers when you make > configuration changes, and sometimes when networks go up and down. Of course I did. And after changing to sendmail.mc I did make in mail directory before restarting the service. > > I still don't get an answer if I try a reverse lookup on the IP. > Perhaps other servers can do it (i.e. the record's there, but hasn't > appeared in the servers that I'm querying). > The strange thing is that me too can't get an answer to reverse name resolution. Anyway, while it works I'll apply that old good method: if it works don't fix it! Thanks again. -- Well thaaat's okay. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: another DNS problem
On Saturday, October 30, 2010 22:30:40 Kevin J. Cummings wrote: > On 10/30/2010 06:16 PM, Hiisi Troll wrote: > > In the provided sendmail.mc file there's an option: > > define(`SMART_HOST', `smtp.direct.ru')dnl I thought it relays all > > my outgoing mail to ISP smtp server. Or am I wrong here? > > Try putting the smtp machine name between square brackets: > > define(`SMART_HOST', `[smtp.direct.ru]')dnl > > there is something about the square brackets and its use to either > use or keep sendmail from using the MX or an A record instead for > the listed host (sorry, I can't remember the details, only that it > works!). I use it (the square brackets) for my ISP's smtp server > and I can send email out through it. The meaning of SMART_HOST is the *MX* host for the name. In other words, sendmail will look up the MX record for smtp.direct.ru to find out what host to connect to. The MX record *could* specify another host -- not smtp.direct.ru . (In this case, there is no MX record for smtp.direct.ru so its A record will be used, which is what you want.) My ISP's relay host does specify a different host for its MX. That host refuses relay from my IP address. To specify a host address instead of the MX host for a domain, place the host address inside of square brackets as Kevin states above. Now even if an MX record someday shows up for that domain name (smtp.direct.ru), its A record will still be used. -- Garry T. Williams -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: another DNS problem
On Sun, 2010-10-31 at 17:42 +0300, Hiisi wrote: > Despite it didn't helped immediately, the problem is gone now. I don't > know what caused it because neither me nor ISP people did nothing to > it at that moment. Strangely, mail queue released and all letters hit > the rcpt to address. Well, the error message said "temporary" failure, with a "deferred" status of the queue. Once the problem goes away, it can retry. Or may just keep retrying, anyway. The obvious question occurs: Had you restarted the mailserver during these tests? You usually have to restart servers when you make configuration changes, and sometimes when networks go up and down. I still don't get an answer if I try a reverse lookup on the IP. Perhaps other servers can do it (i.e. the record's there, but hasn't appeared in the servers that I'm querying). -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: another DNS problem
su, 2010-10-31 kello 17:47 +1030, Tim kirjoitti: <--SNIP--> > > If you cannot set your own reverse DNS, you'll have to ask your ISP (or > mail host) to set it for you. If they cannot, you're stuck. > <--SNIP--> > > Thank you for clarification, Tim! Your responses are always explain the basics of the underlying problem. I've contacted my ISP and domain name provider. They both couldn't find anything wrong in my configuration. I've changed SMART_HOST option in sendmail.mc to bracketed version. Despite it didn't helped immediately, the problem is gone now. I don't know what caused it because neither me nor ISP people did nothing to it at that moment. Strangely, mail queue released and all letters hit the rcpt to address. Probably the culprit is ISP' smtp-server, but I'm not sure here. Now everything work flawlessly and I'm pretty happy with it. As usual, this list is a grate source of quick help. Thanks to everybody. -- It seems that more and more mathematicians are using a new, high level language named "research student". -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: another DNS problem
On Sun, 2010-10-31 at 02:16 +0400, Hiisi Troll wrote: > In the provided sendmail.mc file there's an option: > define(`SMART_HOST', `smtp.direct.ru')dnl > I thought it relays all my outgoing mail to ISP smtp server. Or am I > wrong here? The smart host would be the name of the ISP's mail server. If that's correct, then you should be able to send mail via your own SMTP server, to the ISP's SMTP server, then out to the real world. Just the same as if you'd emailed directly through the ISP's SMTP server. However, you will need to be sending *from* an address that's real to the outside world. i.e. One that anyone in the world would be able to write to, and you receive it. In as much as the domain name has to be real, and have a public IP. Either, because you wrote the message with such a "from address," or your SMTP server masquerades all outgoing mail with such a domain name in the from address. Those are the basics, further restrictions may apply depending on how other parties do their anti-spam protections. If I were to try to post to one of your samples, r...@kello.ru my system (or another's) would be trying to work out the following: Find the MX record for kello.ru dig kello.ru MX ;; ANSWER SECTION: kello.ru. 86400 IN MX 10 mail.kello.ru. So far, so good. Now, we'll have to find the IP address for mail.kello.ru, to make a connection. dig mail.kello.ru ;; ANSWER SECTION: mail.kello.ru. 86307 IN A 212.16.23.132 Now, if that's the correct IP address, then DNS records for your tests should be all fine, and it's another problem that needs resolving. The very basics of email check out. Here's just one thing that might be a problem: Let's try finding the domain name for that IP, as a reverse look-up, as is typically done by various mail servers as part being careful. dig -x 212.16.23.132 And there is no answer. None at all, not even a different domain name (as is commonly the case, when you share IPs with other people). In some cases, because that's a check that many others will do, it will mean "no mail for you!" This can be a problem for, both, incoming and outgoing mail. And if you'd Google searched "451 DNS temporary failure" as in your first posting's error message: "stat=Deferred: 451 DNS temporary failure" You would have found this about two down from the top returned pages: "SMTP Service Info 23 Feb 2004 ... 451 Bad reverse DNS: This is a temporary failure indicating that you are attempting to connect from a host that does not have reverse DNS. ... If you cannot set your own reverse DNS, you'll have to ask your ISP (or mail host) to set it for you. If they cannot, you're stuck. Another problem with trying to send or receive mail from the outside world will depend upon what numerical IPs you have. If it's within the range of addresses handed out by an ISP to their clients, particularly a dynamic address, though still applicable to static address customers, then many other people will not be able to post to you, because their SMTP servers will refuse to make direct connections to customer IPs. Then there's plain old internet racism - you have a .ru top level domain name in your address. Some will blackban that, just for the sake of it. Though, if you're doing local tests, I kind of doubt that other nearby neighbours would be doing that sort of banning. -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: another DNS problem
On 10/30/2010 06:16 PM, Hiisi Troll wrote: > In the provided sendmail.mc file there's an option: > define(`SMART_HOST', `smtp.direct.ru')dnl > I thought it relays all my outgoing mail to ISP smtp server. Or am I > wrong here? Try putting the smtp machine name between square brackets: define(`SMART_HOST', `[smtp.direct.ru]')dnl there is something about the square brackets and its use to either use or keep sendmail from using the MX or an A record instead for the listed host (sorry, I can't remember the details, only that it works!). I use it (the square brackets) for my ISP's smtp server and I can send email out through it. -- Kevin J. Cummings kjch...@rcn.com cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: another DNS problem
la, 2010-10-30 kello 15:56 -0600, Frank Cox kirjoitti: > On Sun, 2010-10-31 at 01:44 +0400, Hiisi wrote: > > However it's impossible to send messages from this machine to the > > outside world. > > because > > > My ISP rejects all outgoing connections to port 25 except to their own > > smtp-server (smtp.direct.ru). > Hi, Frank! In the provided sendmail.mc file there's an option: define(`SMART_HOST', `smtp.direct.ru')dnl I thought it relays all my outgoing mail to ISP smtp server. Or am I wrong here? -- Reading is to the mind what exercise is to the body. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: another DNS problem
On Sun, 2010-10-31 at 01:44 +0400, Hiisi wrote: > However it's impossible to send messages from this machine to the > outside world. because > My ISP rejects all outgoing connections to port 25 except to their own > smtp-server (smtp.direct.ru). -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
another DNS problem
Hi, list! I'm trying to configure my system as a mail server. It's f12. My ISP provides me with a static IP address and I've binded domain name to it (kello.ru) I have sendmail installed and can successfully send messages from remote hosts to users on this machine (i.e. to r...@kello.ru). However it's impossible to send messages from this machine to the outside world. Whenever I'm trying to send messages using mail command or mail function in php-scripts the recipient receives nothing. Instead, I see a lot of messages of this kind in var/log/maillog: Oct 31 01:21:41 kello sendmail[23801]: o9UA6Nvm013215: to=, ctladdr= (0/0), delay=11:15:18, xdelay=00:00:00, mailer=relay, pri=1290432, relay=smtp.direct.ru., dsn=4.0.0, stat=Deferred: 451 DNS temporary failure (#4.3.0) Domain name registrator told me that the MX-record for this domain points to mail.kello.ru which is just an alias for this machine. My ISP rejects all outgoing connections to port 25 except to their own smtp-server (smtp.direct.ru). Here's configuration of this system. cat /etc/hosts 127.0.0.1 localhost.localdomain localhost.localdomain localhost smstools.dyndns-mail.com ::1 localhost.localdomain localhost6 localhost 212.16.23.132 kello.ru mail.kello.ru cat /etc/resolv.conf search ns1.eserver-ru.com nameserver 81.177.8.11 nameserver 81.177.9.11 nameserver 81.177.8.18 cat /etc/mail/sendmail.mc divert(-1)dnl dnl # dnl # This is the sendmail macro config file for m4. If you make changes to dnl # /etc/mail/sendmail.mc, you will need to regenerate the dnl # /etc/mail/sendmail.cf file by confirming that the sendmail-cf package is dnl # installed and then performing a dnl # dnl # /etc/mail/make dnl # include(`/usr/share/sendmail-cf/m4/cf.m4')dnl VERSIONID(`setup for linux')dnl OSTYPE(`linux')dnl dnl # dnl # Do not advertize sendmail version. dnl # dnl define(`confSMTP_LOGIN_MSG', `$j Sendmail; $b')dnl dnl # dnl # default logging level is 9, you might want to set it higher to dnl # debug the configuration dnl # dnl define(`confLOG_LEVEL', `9')dnl dnl # dnl # Uncomment and edit the following line if your outgoing mail needs to dnl # be sent out through an external mail server: dnl # define(`SMART_HOST', `smtp.direct.ru')dnl dnl # define(`confDEF_USER_ID', ``8:12'')dnl dnl define(`confAUTO_REBUILD')dnl define(`confTO_CONNECT', `1m')dnl define(`confTRY_NULL_MX_LIST', `True')dnl define(`confDONT_PROBE_INTERFACES', `True')dnl define(`PROCMAIL_MAILER_PATH', `/usr/bin/procmail')dnl define(`ALIAS_FILE', `/etc/aliases')dnl define(`STATUS_FILE', `/var/log/mail/statistics')dnl define(`UUCP_MAILER_MAX', `200')dnl define(`confUSERDB_SPEC', `/etc/mail/userdb.db')dnl define(`confPRIVACY_FLAGS', `authwarnings,novrfy,noexpn,restrictqrun')dnl define(`confAUTH_OPTIONS', `A')dnl dnl # dnl # The following allows relaying if the user authenticates, and disallows dnl # plaintext authentication (PLAIN/LOGIN) on non-TLS links dnl # dnl define(`confAUTH_OPTIONS', `A p')dnl dnl # dnl # PLAIN is the preferred plaintext authentication method and used by dnl # Mozilla Mail and Evolution, though Outlook Express and other MUAs do dnl # use LOGIN. Other mechanisms should be used if the connection is not dnl # guaranteed secure. dnl # Please remember that saslauthd needs to be running for AUTH. dnl # dnl TRUST_AUTH_MECH(`EXTERNAL DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl dnl define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl dnl # dnl # Rudimentary information on creating certificates for sendmail TLS: dnl # cd /etc/pki/tls/certs; make sendmail.pem dnl # Complete usage: dnl # make -C /etc/pki/tls/certs usage dnl # dnl define(`confCACERT_PATH', `/etc/pki/tls/certs')dnl dnl define(`confCACERT', `/etc/pki/tls/certs/ca-bundle.crt')dnl dnl define(`confSERVER_CERT', `/etc/pki/tls/certs/sendmail.pem')dnl dnl define(`confSERVER_KEY', `/etc/pki/tls/certs/sendmail.pem')dnl dnl # dnl # This allows sendmail to use a keyfile that is shared with OpenLDAP's dnl # slapd, which requires the file to be readble by group ldap dnl # dnl define(`confDONT_BLAME_SENDMAIL', `groupreadablekeyfile')dnl dnl # dnl define(`confTO_QUEUEWARN', `4h')dnl dnl define(`confTO_QUEUERETURN', `5d')dnl dnl define(`confQUEUE_LA', `12')dnl dnl define(`confREFUSE_LA', `18')dnl define(`confTO_IDENT', `0')dnl dnl FEATURE(delay_checks)dnl FEATURE(`no_default_msa', `dnl')dnl FEATURE(`smrsh', `/usr/sbin/smrsh')dnl FEATURE(`mailertable', `hash -o /etc/mail/mailertable.db')dnl FEATURE(`virtusertable', `hash -o /etc/mail/virtusertable.db')dnl FEATURE(redirect)dnl FEATURE(always_add_domain)dnl FEATURE(use_cw_file)dnl FEATURE(use_ct_file)dnl dnl # dnl # The following limits the number of processes sendmail can fork to accept dnl # incoming messages or process its message queues to 20.) sendmail refuses dnl # to accept connections once it has reached its quota of child processes. dnl # dnl define(`confMAX_DAEMON_CHILDREN', `20')dnl dnl # dnl # Limits the number of
Re: DNS problem
On 09/08/2010 07:14 PM, Tim wrote: > On Tue, 2010-09-07 at 16:23 -0700, Wolfgang S. Rupprecht wrote: >> The other thing that may help is runnng your own nameserver. > I've done that for years, and would recommend it to anyone capable of > doing so. All the ISPs I've used have had awful DNS servers, either > sporadically, or permanently. And some practice censorship. > > On the other hand, if you want to practice censorship (sanitising for a > work environment, avoiding distressing your kids, etc.), then running > your own nameserver will work towards helping you control that. > Some people like to use google's public dns servers. Such as 8.8.8.8 and 8.8.4.4. YMMV. -- Let us live!!! Let us love!!! Let us share the deepest secrets of our souls!!! You first. 葛斯克 愛德華 / 台北市八德路四段 signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: DNS problem
On Tue, 2010-09-07 at 16:23 -0700, Wolfgang S. Rupprecht wrote: > The other thing that may help is runnng your own nameserver. I've done that for years, and would recommend it to anyone capable of doing so. All the ISPs I've used have had awful DNS servers, either sporadically, or permanently. And some practice censorship. On the other hand, if you want to practice censorship (sanitising for a work environment, avoiding distressing your kids, etc.), then running your own nameserver will work towards helping you control that. -- [...@localhost ~]$ uname -r 2.6.30.10-105.2.23.fc11.i686.PAE Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: DNS problem
Gordon Charrick writes: > The problem is that when I go to the site or refresh it, I see the > message "Looking up www.kitco.com" in Firefox's status bar for several > seconds before the page comes up. I don't have this problem with any > other web pages and also don't have this problem when I use Firefox on > Windows to go to this site. Do you have some weird anti-scammer protection enabled in firefox? You might want to make sure the "Block reported attack sites" and "Block reported web forgeries" are off (or temporarily turned off). Both of them Firefox to go to some external site to look up each new web server and who knows what sort of delay that induces when those servers are busy. The other thing that may help is runnng your own nameserver. Almost all the external ones are run much worse and have sloppier code than the current named/bind in the yum repositories. -wolfgang -- Wolfgang S. Rupprecht http://www.wsrcc.com/wolfgang/ (IPv6-only) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: DNS problem
On Mon, 2010-09-06 at 09:59 -0700, Gordon Charrick wrote: > The problem is that when I go to the site or refresh it, I see the > message "Looking up www.kitco.com" in Firefox's status bar for several > seconds before the page comes up. I don't have this problem with any > other web pages and also don't have this problem when I use Firefox on > Windows to go to this site. > > Can anyone else confirm this and have an idea what's happening? Use the "dig" tool to query your name servers about that address, and try querying some other name servers. Perhaps you should change the name servers that you're using. -- [...@localhost ~]$ uname -r 2.6.30.10-105.2.23.fc11.i686.PAE Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: DNS problem
Gordon Charrick wrote: > I often use the site www.kitco.com in Firefox. This is a company, in > the US, that deals in precious metals (gold, silver, etc.). > > The problem is that when I go to the site or refresh it, I see the > message "Looking up www.kitco.com" in Firefox's status bar for several > seconds before the page comes up. I don't have this problem with any > other web pages and also don't have this problem when I use Firefox on > Windows to go to this site. > > Can anyone else confirm this and have an idea what's happening? I use > the site a lot because they have graphs and prices that are constantly > updated. > Works over here with ff3.6 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
DNS problem
I often use the site www.kitco.com in Firefox. This is a company, in the US, that deals in precious metals (gold, silver, etc.). The problem is that when I go to the site or refresh it, I see the message "Looking up www.kitco.com" in Firefox's status bar for several seconds before the page comes up. I don't have this problem with any other web pages and also don't have this problem when I use Firefox on Windows to go to this site. Can anyone else confirm this and have an idea what's happening? I use the site a lot because they have graphs and prices that are constantly updated. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: dns problem for wireless connection via NetworkManager
On Tue, Aug 10, 2010 at 11:23 PM, JB wrote: > L gmail.com> writes: > >> ... > Hi, > would that help ? > > man dhclient.conf > prepend ... > append ... > request ... > etc. > > # ls /etc/dhcp* > > JB > Thanks alot. that stuff was hidden in file /etc/dhclient-eth1.conf as prepend domain-name-servers 203.23.236.66,203.23.236.69; > > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > -- Linux Toys http://linuxishbell.wordpress.com/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: dns problem for wireless connection via NetworkManager
L gmail.com> writes: > ... Hi, would that help ? man dhclient.conf prepend ... append ... request ... etc. # ls /etc/dhcp* JB -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: dns problem for wireless connection via NetworkManager
On Tue, Aug 10, 2010 at 10:42 PM, L wrote: > On Tue, Aug 10, 2010 at 10:22 PM, JB wrote: >> L gmail.com> writes: >> >>> ... >>> I check around and can't find where the old DNS nameservers were hidden >>> ... >> >> Hi, >> >> [...@localhost ~]$ cat /etc/resolv.conf >> # Generated by NetworkManager >> domain example.com >> search example.com >> nameserver 127.0.0.1 >> nameserver 1.2.3.4 >> nameserver 5.6.7.8 >> # NOTE: the libc resolver may not support more than 3 nameservers. >> # The nameservers listed below may not be recognized. >> nameserver 9.10.11.12 >> >> JB >> > > This file is auto generated by networkmanager. Altough I set > networkmanager to "IPv4 Settings tab -> IPv4 Settings -> choose > Automatic (DHCP)", It always picks up the old nameservers. > 203.23.236.66 > 203.23.236.69 > > .this is what It generated > > cat /etc/resolv.conf > # Generated by NetworkManager > nameserver 203.23.236.66 > nameserver 203.23.236.69 > nameserver 192.168.1.1 > > I need find where the networkmanager get the dns ( of old ISP): interestingly, if I set up wired connection to "IPv4 Settings tab -> IPv4 Settings -> choose Automatic (DHCP)", it does the right as see below cat /etc/resolv.conf # Generated by NetworkManager nameserver 192.168.1.1 > > >> >> >> -- >> users mailing list >> users@lists.fedoraproject.org >> To unsubscribe or change subscription options: >> https://admin.fedoraproject.org/mailman/listinfo/users >> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines >> > > > > -- > > Linux Toys > http://linuxishbell.wordpress.com/ > -- Linux Toys http://linuxishbell.wordpress.com/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: dns problem for wireless connection via NetworkManager
On Tue, Aug 10, 2010 at 10:22 PM, JB wrote: > L gmail.com> writes: > >> ... >> I check around and can't find where the old DNS nameservers were hidden >> ... > > Hi, > > [...@localhost ~]$ cat /etc/resolv.conf > # Generated by NetworkManager > domain example.com > search example.com > nameserver 127.0.0.1 > nameserver 1.2.3.4 > nameserver 5.6.7.8 > # NOTE: the libc resolver may not support more than 3 nameservers. > # The nameservers listed below may not be recognized. > nameserver 9.10.11.12 > > JB > This file is auto generated by networkmanager. Altough I set networkmanager to "IPv4 Settings tab -> IPv4 Settings -> choose Automatic (DHCP)", It always picks up the old nameservers. 203.23.236.66 203.23.236.69 .this is what It generated cat /etc/resolv.conf # Generated by NetworkManager nameserver 203.23.236.66 nameserver 203.23.236.69 nameserver 192.168.1.1 I need find where the networkmanager get the dns ( of old ISP): > > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > -- Linux Toys http://linuxishbell.wordpress.com/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: dns problem for wireless connection via NetworkManager
On Tue, 2010-08-10 at 19:46 +1000, L wrote: > In the Search Domains text box, type "opennic.glue". I'm not sure if > this is needed, but it never hurt anything in the past. The search domain is what will be appended to hostnames, when you do things using just the hostname. e.g. "ping testname" would become "ping testname.opennic.glue". If hostnames resolve, by themselves. Or your the rest of your networking works perfectly (name resolution, etc., etc.), and your domain name is the same as you'd otherwise have put into the search parameter, then you probably won't see an advantage in manually setting it. But if hostnames don't resolve without the domain name being appended, or you want a different domain name to be appended, then it is an advantage to set that. -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: dns problem for wireless connection via NetworkManager
L gmail.com> writes: > ... > I check around and can't find where the old DNS nameservers were hidden > ... Hi, [...@localhost ~]$ cat /etc/resolv.conf # Generated by NetworkManager domain example.com search example.com nameserver 127.0.0.1 nameserver 1.2.3.4 nameserver 5.6.7.8 # NOTE: the libc resolver may not support more than 3 nameservers. # The nameservers listed below may not be recognized. nameserver 9.10.11.12 JB -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
dns problem for wireless connection via NetworkManager
Hi I use NetworkManager to manage wireless connection following these steps: 1. Right click the network manager icon in the panel and click Edit Connections. 2. Select wireless tab, choose the access ID under Name column, click edit. 3. Click the IPv4 Settings tab. 4. Choose Automatic with manual DNS settings from the Method drop-down box. 5. In the DNS Servers text box, type "71.170.11.156, 216.87.84.209". 6. In the Search Domains text box, type "opennic.glue". I'm not sure if this is needed, but it never hurt anything in the past. 7. Click OK and close the network manager window. This worked ok. but then this causes problem when I changed my ISP, if I alter steps from Step 3 Click the IPv4 Settings tab -> IPv4 Settings -> choose Automatic (DHCP) This always picked up my old DNS (from my old ISP). This is the same problem when I access public wireless points. The DNS nameserver from the public access point was not updated, instead, the old dns nameservers were picked up. I check around and can't find where the old DNS nameservers were hidden can some one offer me a hint? best Y -- Linux Toys http://linuxishbell.wordpress.com/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
