Public DNS Server List. Dns сервер теле2


intoDNS: tele2.se - check DNS server and mail server health

Parent Domain NS records Nameserver records returned by the parent servers are:

pitea.dns.swip.net.   ['192.71.180.43'] (NO GLUE)   [TTL=86400] ystad.dns.swip.net.   ['192.71.220.12'] (NO GLUE)   [TTL=86400] sunic.sunet.se.   ['192.36.125.2']   [TTL=86400]

j.ns.se was kind enough to give us that information.

TLD Parent Check Good. j.ns.se, the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check. Your nameservers are listed Good. The parent server j.ns.se has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers. DNS Parent sent Glue The parent nameserver j.ns.se is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. This happens a lot if you have nameservers on different TLD (domain.com for example with nameserver ns.domain.org.) Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found. NS NS records from your nameserversNS records got from your nameservers listed at the parent NS are:

pitea.dns.swip.net  ['192.71.180.43']   [TTL=1800] ystad.dns.swip.net  ['192.71.220.12']   [TTL=1800] sunic.sunet.se  ['192.36.125.2']   [TTL=1800]

Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone. Same Glue The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below! Glue for NS records INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are: 192.71.220.12192.36.125.2192.71.180.43 You can fix this for example by adding A records to your nameservers for the zones listed above. Mismatched NS records OK. The NS records at all your nameservers are identical. DNS servers responded Good. All nameservers listed at the parent server responded. Name of nameservers are valid OK. All of the NS records that your nameservers report seem valid. Multiple Nameservers Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me. Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain. Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers. Missing nameservers reported by your nameservers OK. All nameservers returned by the parent server j.ns.se are the same as the ones reported by your nameservers. Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. Different subnets OK. Looks like you have nameservers on different subnets! IPs of nameservers are public Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like DNS servers allow TCP connection OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default. Different autonomous systems OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down. Stealth NS records sent Ok. No stealth ns records are sent SOA SOA recordThe SOA record is: Primary nameserver: pitea.dns.swip.net Hostmaster E-mail address: hostmaster.tele2.com Serial #: 2018021201 Refresh: 28800 Retry: 7200 Expire: 604800   1 weeks Default TTL: 3600 NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 2018021201. SOA MNAME entry OK. pitea.dns.swip.net That server is listed at the parent servers. SOA Serial Your SOA serial number is: 2018021201. This appears to be in the recommended format of YYYYMMDDnn. SOA REFRESH OK. Your SOA REFRESH interval is: 28800. That is OK SOA RETRY Your SOA RETRY value is: 7200. Looks ok SOA EXPIRE Your SOA EXPIRE number is: 604800.Looks ok SOA MINIMUM TTL Your SOA MINIMUM TTL is: 3600. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommends a value of 1-3 hours. Your value of 3600 is OK. MX MX RecordsYour MX records that were reported by your nameservers are:

0   mx.tele2.se   94.246.96.190

[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]

Different MX records at nameservers Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs MX name validity Good. I did not detect any invalid hostnames for your MX records. MX IPs are public OK. All of your MX records appear to use public IPs. MX CNAME Check OK. No problems here. MX A request returns CNAME OK. No CNAMEs returned for A records lookups. MX is not IP OK. All of your MX records are host names. Number of MX records OK. Looks like you only have one MX record at your nameservers. You should be careful about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time. Mismatched MX A OK. I did not detect differing IPs for your MX records. Duplicate MX A records OK. I have not found duplicate IP(s) for your MX records. This is a good thing. Reverse MX A records (PTR) Your reverse (PTR) record:190.96.246.94.in-addr.arpa ->  mx.tele2.se You have reverse (PTR) records for all your IPs, that is a good thing. WWW WWW A Record Your www.tele2.se A record is: www.tele2.se  [212.247.238.132]  IPs are public OK. All of your WWW IPs appear to be public IPs. WWW CNAME OK. No CNAME

intodns.com

intoDNS: tele2.com - check DNS server and mail server health

Parent Domain NS records Nameserver records returned by the parent servers are:

falun.dns.swip.net.   ['192.71.220.13']   [TTL=172800] pitea.dns.swip.net.   ['192.71.180.43']   [TTL=172800]

f.gtld-servers.net was kind enough to give us that information.

TLD Parent Check Good. f.gtld-servers.net, the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check. Your nameservers are listed Good. The parent server f.gtld-servers.net has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers. DNS Parent sent Glue Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3) Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found. NS NS records from your nameserversNS records got from your nameservers listed at the parent NS are:

pitea.dns.swip.net  ['192.71.180.43']   [TTL=3600] falun.dns.swip.net  ['192.71.220.13']   [TTL=3600]

Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone. Same Glue The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below! Glue for NS records OK. When I asked your nameservers for your NS records they also returned the A records for the NS records. This is a good thing as it will spare an extra A lookup needed to find those A records. Mismatched NS records OK. The NS records at all your nameservers are identical. DNS servers responded Good. All nameservers listed at the parent server responded. Name of nameservers are valid OK. All of the NS records that your nameservers report seem valid. Multiple Nameservers Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me. Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain. Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers. Missing nameservers reported by your nameservers OK. All nameservers returned by the parent server f.gtld-servers.net are the same as the ones reported by your nameservers. Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. Different subnets OK. Looks like you have nameservers on different subnets! IPs of nameservers are public Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like DNS servers allow TCP connection OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default. Different autonomous systems OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down. Stealth NS records sent Ok. No stealth ns records are sent SOA SOA recordThe SOA record is: Primary nameserver: falun.dns.swip.net Hostmaster E-mail address: hostmaster.tele2.com Serial #: 2018021401 Refresh: 28800 Retry: 7200 Expire: 604800   1 weeks Default TTL: 3600 NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 2018021401. SOA MNAME entry OK. falun.dns.swip.net That server is listed at the parent servers. SOA Serial Your SOA serial number is: 2018021401. This appears to be in the recommended format of YYYYMMDDnn. SOA REFRESH OK. Your SOA REFRESH interval is: 28800. That is OK SOA RETRY Your SOA RETRY value is: 7200. Looks ok SOA EXPIRE Your SOA EXPIRE number is: 604800.Looks ok SOA MINIMUM TTL Your SOA MINIMUM TTL is: 3600. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommends a value of 1-3 hours. Your value of 3600 is OK. MX MX RecordsYour MX records that were reported by your nameservers are:

0   tele2-com.mail.protection.outlook.com   213.199.154.170 213.199.154.234 (no glue)

[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]

Different MX records at nameservers Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs MX name validity Good. I did not detect any invalid hostnames for your MX records. MX IPs are public OK. All of your MX records appear to use public IPs. MX CNAME Check OK. No problems here. MX A request returns CNAME OK. No CNAMEs returned for A records lookups. MX is not IP OK. All of your MX records are host names. Number of MX records OK. Looks like you only have one MX record at your nameservers but that MX record has multiple IPs. You should be careful about what you are doing but overall it's ok. Mismatched MX A OK. I did not detect differing IPs for your MX records. Duplicate MX A records OK. I have not found duplicate IP(s) for your MX records. This is a good thing. Reverse MX A records (PTR) Your reverse (PTR) record:234.154.199.213.in-addr.arpa ->  mail-ve1eur010234.inbound.protection.outlook.com170.154.199.213.in-addr.arpa ->  mail-db5eur010170.inbound.protection.outlook.com You have reverse (PTR) records for all your IPs, that is a good thing. WWW WWW A Record Your www.tele2.com A record is: www.tele2.com  [212.247.238.133]  IPs are public OK. All of your WWW IPs appear to be public IPs. WWW CNAME OK. No CNAME

intodns.com

tele2.ru Domain Health

Javascript is disabled. Javascript is required for this site.

Free Users are allowed only one (1) Domain Health Check every 24 hours. Upgrade to get unlimited Domain Health checks and a free Domain Health Monitor.

Our Domain Health Monitor performs over 30 different tests on your domain every few minutes and immediately alerts you to issues. Learn More

  • Keep tabs on your DNS configuration
  • Monitor your Mail Server to ensure uptime and compliance
  • Check your mail servers against 100+ blacklist
  • Ensure your Web Servers are up and running with valid SSL certificates
These results are for . Did you really mean to run ? Click Here

0 Errors0 Warning0 Passed

Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. Suspendisse et porttitor lectus, quis imperdiet mi. In fermentum ante at risus dictum, eget euismod mi commodo.

0 Errors0 Warning0 Passed

Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. Suspendisse et porttitor lectus, quis imperdiet mi. In fermentum ante at risus dictum, eget euismod mi commodo.

0 Errors0 Warning0 Passed

Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. Suspendisse et porttitor lectus, quis imperdiet mi. In fermentum ante at risus dictum, eget euismod mi commodo.

0 Errors0 Warning0 Passed

Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. Suspendisse et porttitor lectus, quis imperdiet mi. In fermentum ante at risus dictum, eget euismod mi commodo.

0 Errors0 Warning0 Passed

Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. Suspendisse et porttitor lectus, quis imperdiet mi. In fermentum ante at risus dictum, eget euismod mi commodo.

mxtoolbox.com

DNS servers in Kazakhstan

91.185.2.10

ns2.ttc.kz.

9.9.4-RedHat-9.9.4-50.el7_3.1 2018-02-20 valid 100 % Whois 91.185.6.10

ns.ttc.kz.

9.9.4-RedHat-9.9.4-50.el7_3.1 2018-02-20 valid 77 % Whois 178.88.118.133 Almaty dnsmasq-2.47 2018-02-20 valid 97 % Whois 88.151.179.6 2018-02-20 valid 94 % Whois 91.185.1.10

ns.kzhdt.kz.

9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.6 2018-02-20 valid 97 % Whois 88.204.238.134 2018-02-20 valid 100 % Whois 151.236.192.14

mail.ales.kz.

2018-02-20 valid 100 % Whois 92.46.44.18

mail.kipros.kz.

2018-02-20 valid 100 % Whois 85.29.160.211

mail5.theeurasia.kz.

Temirtau Microsoft DNS 6.1.7601 (1DB15CD4) 2018-02-20 valid 100 % Whois 193.193.249.4

smtp.uog.kz.

2018-02-20 valid 100 % Whois 88.204.222.166 Bayqongyr Microsoft DNS 6.1.7601 (1DB144E7) 2018-02-20 valid 100 % Whois 212.154.207.178

ns1.techcenter.kz.

Microsoft DNS 6.1.7600 (1DB04228) 2018-02-20 valid 100 % Whois 212.154.239.78 2018-02-20 valid 90 % Whois 37.151.44.84 Microsoft DNS 6.1.7601 (1DB1446A) 2018-02-20 valid 100 % Whois 89.218.210.84 Microsoft DNS 6.1.7601 (1DB1446A) 2018-02-20 valid 97 % Whois 212.154.228.178 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.1 2018-02-20 valid 100 % Whois 92.46.45.66 dnsmasq-2.48 2018-02-20 valid 94 % Whois 212.154.133.12 Almaty Microsoft DNS 6.1.7601 (1DB15D39) 2018-02-20 valid 97 % Whois 88.204.198.13

l.vista-telekom.kz.

Microsoft DNS 6.0.6002 (17724D35) 2018-02-20 valid 97 % Whois 89.218.174.67 2018-02-20 valid 100 % Whois 212.19.138.2 dnsmasq-2.75 2018-02-20 valid 97 % Whois 212.154.216.169

rastr.com.

2018-02-20 valid 100 % Whois 95.57.155.234 2018-02-20 valid 100 % Whois 212.154.162.130 unknown 2018-02-20 valid 87 % Whois 95.57.155.125 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6 2018-02-20 valid 97 % Whois 212.116.234.13 2018-02-20 valid 100 % Whois 87.247.10.22

fx.ricc.kz.

Microsoft DNS 6.0.6002 (17724D35) 2018-02-20 valid 94 % Whois 213.157.50.130

mail.globalpnp.com.

2018-02-20 valid 100 % Whois 212.19.159.46

di46.alma-di-2.online.kz.

ZyWALL DNS 2018-02-20 valid 45 % Whois 95.57.220.222

mail.esz.kz.

2018-02-20 valid 100 % Whois 93.185.74.226

ns.tower-astana.kz.

2018-02-20 valid 100 % Whois 212.154.234.46 2018-02-20 valid 100 % Whois 95.56.248.228

pdc-1.miras.kz.

Microsoft DNS 6.1.7601 (1DB15D39) 2018-02-20 valid 100 % Whois 88.204.214.122 2018-02-20 valid 100 % Whois 89.250.80.61 2018-02-20 valid 97 % Whois 92.46.223.178

mail.ndtservice.kz.

Microsoft DNS 6.1.7601 (1DB15D39) 2018-02-20 valid 100 % Whois 46.36.144.108 2018-02-20 valid 100 % Whois 88.204.148.243 Almaty 2018-02-20 valid 100 % Whois 89.218.13.90 dnsmasq-2.52 2018-02-20 valid 100 % Whois 89.28.135.41 Ust-Kamenogorsk 2018-02-20 valid 100 % Whois 89.218.67.244 2018-02-20 valid 100 % Whois 89.218.67.245 2018-02-20 valid 100 % Whois 46.19.46.231 Almaty 2018-02-20 valid 100 % Whois 213.157.47.42

mail.m.kgs.kz.

Microsoft DNS 6.0.6002 (17724D35) 2018-02-20 valid 97 % Whois 88.204.253.182 dnsmasq-2.52 2018-02-20 valid 100 % Whois 217.196.20.162

mail.tnsr.kz.

2018-02-20 valid 97 % Whois 89.28.132.221 Ust-Kamenogorsk 2018-02-20 valid 100 % Whois 92.46.237.18 2018-02-20 valid 100 % Whois 91.185.29.2 2018-02-20 valid 100 % Whois 37.150.124.150

37.150.124.150.megaline.telecom.kz.

dnsmasq-2.15 2018-02-20 valid 100 % Whois 89.218.142.170 2018-02-20 valid 100 % Whois 178.88.118.146 Almaty dnsmasq-2.47 2018-02-20 valid 97 % Whois 213.157.57.133

ns.azimut.kz.

2018-02-20 valid 94 % Whois 37.228.67.78 2018-02-20 valid 97 % Whois 77.245.110.207

agsc.kz.

Microsoft DNS 6.1.7601 (1DB15D39) 2018-02-20 valid 97 % Whois 89.218.2.99

89.218.2.99.static.telecom.kz.

2018-02-20 valid 100 % Whois 91.147.96.169 Microsoft DNS 6.0.6002 (17724D35) 2018-02-20 valid 90 % Whois 91.147.112.14

mail.borkit.com.

2018-02-20 valid 100 % Whois 91.185.3.50 Version: recursive-main/20717463 2018-02-20 valid 100 % Whois 85.29.137.49 2018-02-20 valid 100 % Whois 195.189.30.58 Almaty Microsoft DNS 6.1.7601 (1DB15CD4) 2018-02-20 valid 100 % Whois 82.200.209.98

ns-2.nok.kz.

Microsoft DNS 6.1.7601 (1DB15D39) 2018-02-20 valid 100 % Whois 87.247.12.140 2018-02-20 valid 100 % Whois 178.88.161.200 2018-02-20 valid 100 % Whois 89.218.133.36 2018-02-20 valid 100 % Whois 89.218.133.35 2018-02-20 valid 100 % Whois 178.89.7.118 2018-02-20 valid 71 % Whois 178.90.136.102 2018-02-20 valid 100 % Whois 217.196.16.122

mail.anaco.kz.

2018-02-20 valid 97 % Whois 89.218.146.66 dnsmasq-2.52 2018-02-20 valid 90 % Whois 92.46.40.50 2018-02-20 valid 100 % Whois 88.204.180.222 2018-02-20 valid 100 % Whois 151.236.192.174

mail.realinvest.kz.

9.8.5-rl.13214.22-P2 2018-02-20 valid 81 % Whois 88.204.181.90

dd.atf-policy.kz.

dnsmasq-2.52 2018-02-20 valid 100 % Whois 85.29.136.60 Microsoft DNS 6.1.7601 (1DB1446A) 2018-02-20 valid 100 % Whois 212.154.175.202 ZyWALL DNS 2018-02-20 valid 100 % Whois 89.218.210.83 Microsoft DNS 6.1.7600 (1DB04001) 2018-02-20 valid 100 % Whois 212.154.131.115

mail.kgnt.kz.

Almaty Microsoft DNS 6.1.7601 (1DB14556) 2018-02-20 valid 97 % Whois 93.185.71.166 2018-02-20 valid 100 % Whois 77.245.99.170

smtp.uog.kz.

2018-02-20 valid 97 % Whois 212.154.167.215

mail.mgd.kz.

2018-02-20 i/o timeout 0 % Whois 89.218.24.194 2018-02-20 i/o timeout 0 % Whois 217.196.23.18

mail.atcs.kz.

2018-02-20 i/o timeout 0 % Whois 178.91.95.226 2018-02-20 i/o timeout 0 % Whois 92.46.49.13 ZyWALL DNS 2018-02-20 SERVFAIL for example.com 39 % Whois 212.19.159.50

di50.alma-di-2.online.kz.

ZyWALL DNS 2018-02-20 SERVFAIL for non-existent.example.com 35 % Whois 85.29.148.9

ukg.2day.kz.

2018-02-20 i/o timeout 0 % Whois 109.163.199.26 2018-02-20 Unexpected result for example.com: NXDOMAIN 81 % Whois 88.204.132.101

ns.a-a.kz.

2018-02-20 i/o timeout 0 % Whois 88.204.198.136

88.204.198.136.metro.online.kz.

2018-02-20 i/o timeout 0 % Whois 95.57.155.146 2018-02-20 i/o timeout 0 % Whois 212.154.162.135 2018-02-20 i/o timeout 0 % Whois 212.154.163.30 2018-02-20 i/o timeout 45 % Whois 82.200.178.146 2018-02-20 i/o timeout 0 % Whois 82.115.52.102

dalem.kz.

2018-02-20 i/o timeout 19 % Whois 89.218.69.130 2018-02-20 i/o timeout 0 % Whois 80.242.214.147

mail.btas.kz.

2018-02-20 i/o timeout 0 % Whois 212.116.229.137 2018-02-20 connection refused 0 % Whois 95.59.27.182 ICS DNS Server 2018-02-20 REFUSED for example.com 0 % Whois 95.57.215.130 2018-02-20 i/o timeout 0 % Whois

public-dns.info

Listed DNS Servers

Please consult this page, if you do not know which DNS servers to use. If you know the IP addresses of some DNS servers that are not listed on this page, please post that information on our Forum. Thanks!

Google DNS Primary: 8.8.8.8 Secondary: 8.8.4.4Australia

QLD144.140.70.29144.140.71.15144.140.70.16

Westnet (ADSL)203.21.20.20203.10.1.9

Canada

Shaw Cable64.59.144.1664.59.144.17

Telus(BC)154.11.128.129154.11.128.150154.11.128.1154.11.128.2154.11.128.130209.53.4.150

China

I-Cable (Hong Kong)210.80.60.1210.80.60.2

Italy

Alice 212.216.112.112212.216.172.62

Malaysia

Schoolnet (ADSL)202.75.44.18203.106.3.171202.75.44.20

Tmnet Streamyx (ADSL)202.188.0.132202.188.0.133 202.188.0.147202.188.0.161202.188.0.181202.188.0.182202.188.1.4202.188.1.5202.188.1.23202.188.1.25

Mexico

Cablemas (Cable 128kbps)69.44.143.245 200.79.192.3

Nederland Hetnet 10.0.0.5 10.0.0.2 10.0.0.3

Planet Internet195.121.1.34195.121.1.66

New Zealand

Xtra (DSL)202.27.158.40202.27.156.72

Paradise (DSL)203.96.152.4203.96.152.12

Portugal

Netvis�o (Cable) 213.228.128.6213.228.128.5

TVTel195.22.0.204 195.22.0.205

Sweden

Tele2130.244.127.161130.244.127.169

United Kingdom

AOL205.188.146.145

Blueyonder/Telewest (Cable)193.38.113.3194.177.157.4

BTInternet194.73.73.172194.73.73.173194.72.9.44194.72.9.38 (Cardiff, S.Wales)194.72.9.39 (Cardiff, S.Wales)

Bulldog BroadbandNs3.bulldogdsl.com . 83.146.21.5 (South)Ns4.bulldogdsl.com . 83.146.21.6 (South)Ns5.bulldogdsl.com . 212.158.248.5 (North)Ns6.bulldogdsl.com . 212.158.248.6 (North)

Nildram (ADSL)213.208.106.212213.208.106.213

NTL (Cable) and Virgin.net (ADSL)194.168.4.100194.168.8.100

Pipex (ADSL)62.241.162.35 62.189.34.83

Silvermead (Satellite, DSL, ISDN)62.55.96.22662.55.96.109 (unchecked)

Telewest (Cable)62.31.176.39194.117.134.19

Tiscali, Screaming.net, Worldonline, Lineone212.74.112.66212.74.112.67212.74.114.129 (Cambridge)212.74.114.193 (Cambridge)

Wanadoo UK (ADSL)195.92.195.94195.92.195.95

Zen InternetPrimary DNS: 212.23.8.1Secondary DNS: 212.23.3.1

United States of America

Adelphia67.21.13.4 Los Angeles, CA67.21.13.2 Los Angeles, CA24.48.217.226 Santa Monica, CA24.48.217.227 Santa Monica, CA68.168.1.42 Florida68.168.1.46 Florida

Bellsouth Fast access DSL:Georgia205.152.37.23205.152.37.24205.152.37.25205.152.144.24205.152.144.25

Charter Comms (Cable)68.116.46.70

Comcast (pick the nearest!)68.87.66.196 Comcast (national) Primary DNS Server.68.87.64.196 Comcast Secondary DNS Server.68.57.32.5 (Virginia)68.57.32.6 (Virginia)216.148.227.68 (Denver, Colorado)204.127.202.4 (Denver, Colorado)68.42.244.5 (Taylor, Michigan)68.42.244.6 (Taylor, Michigan)68.62.160.5 (Huntsville, Alabama)68.62.160.6 (Huntsville, Alabama)68.87.96.3 (Pennsylvania)68.87.96.4 (Pennsylvania)

Cox HSI (Cable)68.12.16.25 (Oklahoma - Primary)68.12.16.30 (Oklahoma - Secondary)68.2.16.30 (Oklahoma - Tertiary)

Cox.net68.10.16.2568.10.16.3068.9.16.30

Earthlink - seem to be shared by Cable and DSL users in several states. Georgia and Florida confirmed.207.69.188.187207.69.188.186207.69.188.185209.86.63.217 (Cable) - Charlotte, NC

Harrisonville Telephone Company (HTC)216.114.114.130 (Illinois)216.114.114.132 (Illinois)

Horry Telephone Coop66.153.128.98 (Horry County, South Carolina)66.153.162.98 (Horry County, South Carolina)

ORSC Public Access DNS Nameservers (Anyone can use these, no matter what ISP)199.166.24.253199.166.27.253199.166.28.10199.166.29.3199.166.31.3195.117.6.25204.57.55.100

Roadrunner (Cable)24.25.195.1 (San Diego, CA)24.25.195.2 (San Diego, CA)24.25.195.3 (San Diego, CA)

SBC Yahoo DSL206.13.31.13206.13.28.60206.13.31.5206.13.28.31

Speakeasy (pick any two!)66.93.87.2 (Washington state and Oregon)216.231.41.2 (Washington DC - probably)216.254.95.2 (NY, Massachusetts and Pennsylvania)64.81.45.2 (Los Angeles, California)64.81.111.2 (Denver, Colorado)64.81.127.2 (Dallas, Texas)64.81.79.2 (Sacramento, California)64.81.159.2 (Baltimore and Washington DC)66.92.64.2 (Boston, Massachusetts)66.92.224.2 (Philadelphia)66.92.159.2 (Washington DC)216.27.175.2 (Atlanta, Georgia. Serves Florida too)

Sprintlink (nationwide)204.117.214.10199.2.252.10204.97.212.10

TimeWarner24.93.1.119 (Rochester, NY)

Unicom 216.104.64.5 (Grants Pass, OR)216.104.72.5 (Portland, OR)

FrontierNet / Citlink / New North DNS addresses:66.133.170.2 (Rochester, NY)170.215.255.114 (Rochester, NY)216.67.192.3 (Arizona)207.173.225.3 (Arizona)207.173.225.3 (California)216.67.192.3 (California)170.215.255.114 (New York (areas other than Rochester))66.133.170.2 (New York (areas other than Rochester))170.215.184.3 (West Virginia)170.215.126.3 (West Virginia)170.215.126.3 (Tennessee, Georgia)170.215.184.3 (Tennessee, Georgia)67.50.135.146 (Illinois)66.133.191.35 (Illinois)66.133.191.35 (Wisconsin, Minnesota, Iowa, North Dakota and Nebraska)170.215.255.114 (Wisconsin, Minnesota, Iowa, North Dakota and Nebraska)

Suddenlink DNS Numbers209.55.0.110209.55.1.220Verizon (Level3) - these are not restricted to Verizon customers4.2.2.14.2.2.24.2.2.34.2.2.44.2.2.54.2.2.6

Wave Broadband24.113.32.2924.113.32.30

portforward.com

Quickly set DNS servers of your Internet connection on Windows

 
QuickSetDNS v1.15 - Quickly set DNS servers of your Internet connection on Windows Copyright (c) 2013 - 2015 Nir Sofer
Description
QuickSetDNS is a simple tool that allows you to easily change the DNS servers that are used for your Internet connection. You can set the desired DNS servers from the user interface, by choosing from a list of DNS servers that you defined, or from command-line, without displaying any user interface.

System Requirements
This utility works on any version of Windows, starting from Windows 2000 and up to Windows 10. Both 32-bit and 64-bit systems are supported.
Versions History
  • Version 1.15:
    • Added 'Open Adapter In RegEdit' option, which allows you to open the settings of the selected network adapter in the Registry.
    • You can now manually set the DNS servers in the Registry, and then use /SetDNS command with 'reg' value to update the system with the Registry changes you made, for example: QuickSetDNS /SetDNS reg "{F41A4233-02DA-42D6-A97B-A2D12F9FE0CD}"
  • Version 1.10:
    • Added option to choose another font (name and size) to display in the main window.
  • Version 1.05:
    • Added 'Put Icon On Tray' option.
  • Version 1.03:
    • Fixed bug: On some systems, QuickSetDNS failed to display network adapters in the top combo-box.
  • Version 1.02:
    • Added 'Always On Top' option.
  • Version 1.01:
    • Added 'Router DNS' item, which allows you to choose the internal DNS server of your router.
  • Version 1.00 - First release.
Start Using QuickSetDNS
QuickSetDNS doesn't require any installation process or additional dll files. In order to start using it, simply run the executable file - QuickSetDNS.exe

After running QuickSetDNS, the main window allows you to easily choose the desired DNS servers to use on your Internet connection, by using the 'Set Active DNS' option (F2). By default, QuickSetDNS provides only one alternative: the public DNS servers of Google - 8.8.8.8 and 8.8.4.4 You can easily add more DNS servers to the list by using the 'New DNS Server' option (Ctrl+N).

If the 'Automatic DNS' option is selected, then the DNS server information is received from your router automatically, using DHCP.

If you have multiple network adapters, you may need to choose the correct network adapter from the combo-box located just below the toolbar of QuickSetDNS.

Setting DNS servers from command-line
With QuickSetDNS, you can easily set the desired DNS servers from command-line, without displaying any user intertface by using the /SetDNS command:

QuickSetDNS.exe /SetDNS [DNS Servers List] [Network Adapter String]

[DNS Servers List] specifies the DNS servers, delimited by comma if there are multiple servers. If empty string is specified ( "" ), QuickSetDNS will set the automatic DNS mode. if 'reg' string is specified , QuickSetDNS will not set the DNS, but it'll update the system with the DNS changes you made in the Registry (Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\\arameters\\nterfaces\[Adapter] ). [Network Adapter String] specifies the unique ID string of your network adapter. If you don't know what is your Network Adapter String, simply press Ctrl+L (Copy SetDNS Command-Line) and the entire command needed to set the selected DNS server will be copied to the clipboard. If empty string is specified ( "" ), QuickSetDNS will try to choose the correct network adapter automatically.

Here's some examples for the /SetDNS command: QuickSetDNS.exe /SetDNS "8.8.8.8,8.8.4.4" "{F41A4233-02DA-42D6-A97B-A2D12F9FE0CD}" QuickSetDNS.exe /SetDNS "8.8.8.8,8.8.4.4" QuickSetDNS.exe /SetDNS "" "{F41A4233-02DA-42D6-A97B-A2D12F9FE0CD}" QuickSetDNS.exe /SetDNS "" QuickSetDNS.exe /SetDNS "192.168.1.1" "{F41A4233-02DA-42D6-A97B-A2D12F9FE0CD}" QuickSetDNS.exe /SetDNS "reg" "{F41A4233-02DA-42D6-A97B-A2D12F9FE0CD}"

Translating QuickSetDNS to other languages
In order to translate QuickSetDNS to other language, follow the instructions below:
  1. Run QuickSetDNS with /savelangfile parameter: QuickSetDNS.exe /savelangfile A file named QuickSetDNS_lng.ini will be created in the folder of QuickSetDNS utility.
  2. Open the created language file in Notepad or in any other text editor.
  3. Translate all string entries to the desired language. Optionally, you can also add your name and/or a link to your Web site. (TranslatorName and TranslatorURL values) If you add this information, it'll be used in the 'About' window.
  4. After you finish the translation, Run QuickSetDNS, and all translated strings will be loaded from the language file. If you want to run QuickSetDNS without the translation, simply rename the language file, or move it to another folder.
License
This utility is released as freeware. You are allowed to freely distribute this utility via floppy disk, CD-ROM, Internet, or in any other way, as long as you don't charge anything for this and you don't sell it or distribute it as a part of commercial product. If you distribute this utility, you must include all files in the distribution package, without any modification !
Disclaimer
The software is provided "AS IS" without any warranty, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The author will not be liable for any special, incidental, consequential or indirect damages due to loss of data or any other reason.
Feedback
If you have any problem, suggestion, comment, or you found a bug in my utility, you can send a message to [email protected] QuickSetDNS is also available in other languages. In order to change the language of QuickSetDNS, download the appropriate language zip file, extract the 'quicksetdns_lng.ini', and put it in the same folder that you Installed QuickSetDNS utility.   

www.nirsoft.net

Use OpenDNS

If your ISP is having issues with its DNS service, switching to OpenDNS' DNS will get you back online in just a few quick steps. Follow the instructions for your operating system or router below.

If you have friends, family, or colleagues who have the same ISP as you, send them this info to help them get back online. Text them or call them with the IP address http://208.69.38.205.

Or, tell your Twitter followers that they can get back online by following the instructions on http://208.69.38.205.

Questions? Tweet @OpenDNS for assistance getting set up.

Where will you be setting up OpenDNS?

Mac OS X

  1. Go to System Preferences.
  2. Click on Network.
  3. Select the first connection in your list and click Advanced.
  4. Select the DNS tab and add 208.67.222.222 and 208.67.220.220 to the list of DNS servers.
  5. Click OK

Windows 7

  1. Click the Start Orb, then select Control Panel.
  2. Click on Network and Sharing Center.
  3. Click on your primary connection or Local Area Connection under Active Networks.
  4. Click the Properties button.Windows 7 may prompt you for permission to make network setting changes.
  5. Highlight 'Internet Protocol Version 4' and click Properties.
  6. Click the radio button 'Use the following DNS server addresses:' and type 208.67.222.222 and 208.67.220.220 in the Preferred DNS server and Alternate DNS server fields.
  7. Click OK button, then the Close button, then Close again. Finally, close the Network and Sharing Center window.At this point, we highly suggest that you flush your DNS resolver cache and web browser caches to ensure that your new configuration settings take effect.

Windows XP

  1. Select Control Panel from the Start menu.
  2. Click Network Connections from the Control Panel choices.
  3. Choose your connection from the Network Connections window.If you have more than one, choose your default/current connection.
  4. Click Properties button.
  5. Select Internet Protocol (TCP/IP) and click Properties.
  6. Click the radio button Use the following DNS server addresses and type 208.67.222.222 and 208.67.220.220 in the Preferred DNS server and Alternate DNS server fields.
  7. Click OK

Windows Vista

  1. Click the Start Orb, then select Control Panel.
  2. Click on View network status and tasks.
  3. Click on View status.
  4. Click the Properties button.
  5. Vista may ask for your permission to make changes. If so, click the Continue button.
  6. Select Internet Protocol Version 4 (TCP/IPv4), then click the Properties button.
  7. Click the radio button "Use the following DNS server addresses:" and type in OpenDNS addresses, 208.67.222.222 and 208.67.220.220, in the Preferred DNS server and Alternate DNS server fields.
  8. Click the OK button, then the Close button, and the Close button again. Close the Network and Sharing Center window.

Generic Router

  1. Open the preferences for your router.

    Often, the preferences are set in your web browser, via a URL with numbers (example: http://192.168.0.1). You may need a password.

    If you're like us, and you set the router password long ago and cannot remember it now, you can often reset the password to the manufacturer default by pressing a button on the router itself.

    Or preferences may be set via specific application for your router, which you installed on your computer when you added the router.

  2. Find the DNS server settings.Scan for the letters DNS next to a field which allows two or three sets of numbers, each broken into four groups of one to three numbers.
  3. Put in the OpenDNS server addresses, 208.67.222.222 and 208.67.220.220, as your DNS server settings and save/apply.

Linksys Router

  1. Visit the router's IP address in a new browser window.http://192.168.1.1 is the default Linksys router IP address.
  2. Enter the Network password.The "Enter Network Password" window will appear. Skip user name and type the router's password (admin is the default password, if you haven't changed it) and click the OK button.
  3. Type in OpenDNS addresses, 208.67.222.222, 208.67.220.220, in Static DNS 1 and Static DNS 2 fields.
  4. Click Save Settings button.

Netgear Router

  1. Type the router's setup URL (http://www.routerlogin.net, http://192.168.0.1 or http://192.168.1.1) into a web browser address bar.http://192.168.1.1 is the default Netgear router IP address.
  2. Enter the password.
  3. Type in OpenDNS addresses, 208.67.222.222 and 208.67.220.220, in Primary DNS and Secondary DNS fields.
  4. Click Apply button.
  5. Wait for the settings to be updated.

D-Link Router

  1. Visit the router's IP address (http://192.168.0.1) in a new browser window.If you are attempting to configure a D-Link router, take note of your computer's Default Gateway IP address. The Default Gateway is the IP address of the D-Link router. By default, it should be 192.168.0.1. Most D-Link devices use the 192.168.0.X range.
  2. Enter the router password.Note: if you have not changed the original settings, the default username is admin and the password is blank (nothing).
  3. Click on the Manual Internet Connection Setup button at the bottom.
  4. Enter the OpenDNS addresses, 208.67.222.222 and 208.67.220.220, in Primary DNS Server and Secondary DNS Server fields.
  5. Click Save Settings button at the top.

use.opendns.com


Смотрите также