|
Re: HowTo setup DNS 2 Years ago
|
|
Thank you Tim and Nick,
I tried to write down all the steps that I made.
The idea was, when it's solved and I learned how to properly set it up, to make more sense in just the 1st post of this thread.
At a later time I will collect the bare basics and my current status, to see if that could provide a more clear view of this issue ... what is not easily done since I am still learning ... 
Greetings,
John |
|
John
Platinum Boarder
Posts: 1282
|
|
|
|
|
Re: HowTo setup DNS 2 Years ago
|
|
This is one feature that always seem to make me what to throw my ClearOS out the window... Just before I do, it works! 
John, sorry to jump in after a day late here.
Here is what I did to ensure that it everything works...
1) Setup domain cname and I'm assuming you're using ClearSDN.
2) Setup a website (Server --- WEB --- WEB SERVER) using the subdomain.domain.com
3) Make sure that you remove the *.subdomain.domain.com from the website.
4) Create your FlexShare and enable it.
This will ensure that the subdomain is access outside your LAN and I'm sure it works inside the LAN too... but than again it might only work because it's accessible outside the LAN... I'll check.
Edit: I did check, but I have some extra settings in the vhost file that might enable it without the webconfig. SO, it does work. I'm assuming that it goes outside the LAN to query it, then returns to the LAN to find it....
I hope that helps. |
|
|
|
Last Edit: 2011/04/28 09:36 By kevin.dika.
|
|
|
Re: HowTo setup DNS 2 Years ago
|
|
Hi Kevin,
Thanks for sharing and giving your input.
I tried the steps that you mention in 3 ways.
A virtual COS box in standalone mode At another location in standalone mode.
For the time being, I will not be at the location with the standalone box, so my troubleshooting will have to wait.
The "additional" settings in your vhost, might be the reason why it works for you, but for now I am still at a loss.
Next time I am on location I will attempt to continue troubleshooting.
Greetings,
John |
|
John
Platinum Boarder
Posts: 1282
|
|
|
|
|
Re: HowTo setup DNS 2 Years ago
|
|
The only additions I put in the vhost was the fact to allow outside LAN uses.
Give me one sec, and I'll post what I have there... to see if they are are different.
Yeah I didn't think anything special. I have a few special features on that site... but that is because I run a special index addition to it.
| Code: |
<VirtualHost *:80>
ServerName subdomain.domain.com
ServerAlias subdomain.domain.com
DocumentRoot /var/www/virtual/subdomain.domain.com
ErrorLog /var/log/httpd/subdomain.domain.com_error_log
CustomLog /var/log/httpd/subdomain.domain.com_access_log combined
</VirtualHost>
<Directory "/var/flexshare/shares/subdomain">
AllowOverride All
Order allow,deny
Allow from all
<IfModule mod_autoindex.c>
Options Indexes FollowSymLinks
IndexOptions FancyIndexing
IndexOptions VersionSort
IndexOptions HTMLTable
IndexOptions FoldersFirst
IndexOptions IconsAreLinks
IndexOptions IgnoreCase
IndexOptions SuppressDescription
IndexOptions SuppressHTMLPreamble
IndexOptions XHTML
IndexOptions IconWidth=16
IndexOptions IconHeight=16
IndexOptions NameWidth=*
IndexOrderDefault Descending Name
HeaderName /index-style/header.html
ReadmeName /index-style/footer.html
</ifModule>
</Directory>
|
httdp.conf files
[code]
Alias /flexshare/subdomain /var/flexshare/shares/subdomain
<VirtualHost *:80>
ServerName subdomain.domain.com
DocumentRoot /var/flexshare/shares/subdomain
ErrorLog /var/log/httpd/domain.com_error_log
CustomLog /var/log/httpd/domain.com_access_log common
</VirtualHost>
<Directory /var/flexshare/shares/subdomain>
Options -Indexes -FollowSymLinks -IncludesNOExec
Order deny,allow
Allow from all
RemoveHandler .php
AddType application/x-httpd-php-source .php
</Directory> |
|
|
|
Last Edit: 2011/04/29 09:02 By kevin.dika.
|
|
|
Re: HowTo setup DNS 2 Years ago
|
|
|
Yeah, I can see what you mean now..
So I was doing some more "testing" and the option that ALLOWS for internal use of the domain is and must "Allow All" access.
However,
Modifying the Host file does allow you to access it internal only.
But I'm assuming there is some type of bug happens with the modifying the host file, because when you do, it will read differently within the webconfig. So I'm guessing this is the bug that Tim placed a request for.
But by the sounds of it, it looks like you are trying to access a local internet address from two different locations.
|
|
|
|
|
|
|
Re: HowTo setup DNS 1 Year, 8 Months ago
|
|
Hi all,
Now that I've finally learned how to create a flowchart, I would like to present the following model:
As simple as this looks, it still doesn't work ... 
I still cannot access Flexshares with the domain names I setup in "Network - Settings - Local DNS Server".
Please advice,
John |
|
John
Platinum Boarder
Posts: 1282
|
|
|
|
|
Re: HowTo setup DNS 1 Year, 8 Months ago
|
|
|
I believe that "bump" is the correct term for this ...
Is there anyone who can tell me what is wrong with my DNS setup ... ?!?
I am still unable to fully use domain & host names and the problem occurs with 3 different modem/routers ... including with a cos gateway. (<ip address> works, but <domain.lan> doesn't.)
Only some flexshares work, but that is not acceptable ... I mean ... how hard can this be ...
Please advice,
John
|
|
John
Platinum Boarder
Posts: 1282
|
|
Last Edit: 2011/09/11 16:17 By Blanco.
|
|
|
Re: HowTo setup DNS 1 Year, 8 Months ago
|
|
John,
Can you use the nslookup command on any hosts (windows or linux) you are trying to use to access the flexshares via DNS? (note, you'll have to use either the fully qualified domain name of your flexshare/ClearOS box or its IP address in place of "flexshare.example.net".
| Code: |
nslookup flexshare.example.net
|
If you don't get an answer here, you need to look at your DNS settings first. I'd suggest you point all of your internal clients to your ClearOS box. This will allow the ClearOS box to do any DNS lookups that are local to it (think flexshares), your ISP, OpenDNS, Google will have _no_ idea how to resolve the flexshare's IP without you manually configuring some sort of "external" DNS service to do so.
You can also use the nslookup command to do resolution via a specific DNS server (the previous example will use whatever DNS server your client gets via a static/DHCP config).
| Code: |
nslookup
server 8.8.8.8
nslookup flexshare.example.net
|
The above example will fail absent the "external" DNS service I noted above.
Next, try this.
Use your ClearOS box that is hosting the flexshares to do the DNS resolution. (you will need to have UDP port 53 open in the firewall of your ClearOS box and the dnsmasq service running on your ClearOS box for this to work.
| Code: |
nslookup
server flexshare.example.net
nslookup flexshare.example.net
|
If this fails, then you've got some issue with the DNS service running on your ClearOS box.
Please post the output of the above command examples here and I might be able to provide some insight. |
|
|
|
|
|
|
Re: HowTo setup DNS 1 Year, 8 Months ago
|
|
Hi Bob,
Thanks for responding.
Manually pointing the clients DNS to the COS box is not an option, because we have a lot of circulation of clients.
Port 53 UDP & TCP are both open on the standalone COS box.
AFAIK dnsmasq never runs on a standalone COS box.
Here are some of the requested results from a client that has an 'obtain DNS automatically' setup:
| Code: |
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>NSLOOKUP flexshare.gallery.lan
Server: dns.<abcde>.net
Address: <DNS ISP>
*** dns.<abcde>.net can't find flexshare.gallery.lan: Non-existent domain
C:\>NSLOOKUP 192.168.1.100/flexshare/gallery
Server: dns.<abcde>.net
Address: <DNS ISP>
*** dns.<abcde>.net can't find 192.168.1.100/flexshare/gallery: Non-existent domain
C:\>NSLOOKUP <domain>.lan/flexshare/gallery
Server: dns.<abcde>.net
Address: <DNS ISP>
*** dns.<abcde>.net can't find <domain>.lan/flexshare/gallery: Non-existent domain
C:\>NSLOOKUP <domain>.poweredbyclear.com/flexshare/gallery
Server: dns.<abcde>.net
Address: <DNS ISP>
*** dns.<abcde>.net can't find <domain>.poweredbyclear.com/flexshare/gallery: Non-existent domain
|
I hope that with this information you or someone else will be able to guide me in the right direction.
Greetings,
John |
|
John
Platinum Boarder
Posts: 1282
|
|
Last Edit: 2011/09/16 12:52 By Blanco.
|
|
|
Re:HowTo setup DNS 1 Year, 8 Months ago
|
|
John,
DNS can be a complicated beast, but I'll try to explain what I _think_ is going on with your setup. I'll use your examples as I explain.
| Code: |
C:\>NSLOOKUP flexshare.gallery.lan
Server: dns.tb.iss.as9143.net
Address: 212.54.40.25
*** dns.tb.iss.as9143.net can't find flexshare.gallery.lan: Non-existent domain
|
1) The DNS server you are using "dns.tb.iss.as9143.net" has no knowledge of any hosts on "gallery.lan". In fact, "lan" is not even a real Top Level Domain (TLD). See this wiki article to read up on TLDs. The "whois" command when run against as9143.net" confirms this:
| Code: |
:~$ whois as9143.net
Whois Server Version 2.0
Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.
Domain Name: AS9143.NET
Registrar: REALTIME REGISTER BV
Whois Server: whois.yoursrs.com
Referral URL: http://www.realtimeregister.com
Name Server: NS1.GN.ISS.AS9143.NET
Name Server: NS1.GV.ISS.AS9143.NET
Name Server: NS1.MND.ISS.AS9143.NET
Name Server: NS1.TB.ISS.AS9143.NET
Status: clientTransferProhibited
Updated Date: 16-nov-2010
Creation Date: 16-nov-2004
Expiration Date: 16-nov-2011
>>> Last update of whois database: Wed, 14 Sep 2011 01:54:08 UTC <<<
NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.
TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.
The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.
Domain Name:as9143.net
Name Server:ns1.gn.iss.as9143.net
Name Server:ns1.gv.iss.as9143.net
Name Server:ns1.mnd.iss.as9143.net
Name Server:ns1.tb.iss.as9143.net
Created On:2009-05-08
Last Updated On:2010-11-16
Expiration Date:2011-11-16
Dealer:ziggo
Registrant ID:Ziggo_bv
Registrant Name:ISP Management
Registrant Organization:Ziggo B.V.
Registrant Street1:Atoomweg 100
Registrant Street2:
Registrant Street3:
Registrant City:Utrecht
Registrant State/Province:
Registrant Postal Code:3542 AB
Registrant Country:NL
Registrant Phone:+31.388528000
Registrant Fax:
Registrant Email:dnsadmin@as9143.net
Admin ID:Ziggo_bv
Admin Name:ISP Management
Admin Organization:Ziggo B.V.
Admin Street1:Atoomweg 100
Admin Street2:
Admin Street3:
Admin City:Utrecht
Admin State/Province:
Admin Postal Code:3542 AB
Admin Country:NL
Admin Phone:+31.388528000
Admin Fax:
Admin Email:dnsadmin@as9143.net
Billing ID:Ziggo_bv
Billing Name:ISP Management
Billing Organization:Ziggo B.V.
Billing Street1:Atoomweg 100
Billing Street2:
Billing Street3:
Billing City:Utrecht
Billing State/Province:
Billing Postal Code:3542 AB
Billing Country:NL
Billing Phone:+31.388528000
Billing Fax:
Billing Email:dnsadmin@as9143.net
Tech ID:Ziggo_bv
Tech Name:ISP Management
Tech Organization:Ziggo B.V.
Tech Street1:Atoomweg 100
Tech Street2:
Tech Street3:
Tech City:Utrecht
Tech State/Province:
Tech Postal Code:3542 AB
Tech Country:NL
Tech Phone:+31.388528000
Tech Fax:
Tech Email:dnsadmin@as9143.net
|
| Code: |
:~$ dig dns.tb.iss.as9143.net
; <<>> DiG 9.7.0-P1 <<>> dns.tb.iss.as9143.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8794
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;dns.tb.iss.as9143.net. IN A
;; ANSWER SECTION:
dns.tb.iss.as9143.net. 85991 IN A 212.54.40.25
;; Query time: 47 msec
;; SERVER: *.*.*.*
;; WHEN: Tue Sep 13 19:01:01 2011
;; MSG SIZE rcvd: 55
|
2) ClearOS boxes will ask you to configure a Domain when you install them that is used in the LDAP server and DHCP server (among other things). If your computers on the local network are using this box as their DHCP/DNS server, they should be able resolve the server's IP, and any other IP address/hostname pairs that you define in the web interface in the Network -> Settings -> Local DNS Server interface.
3) The servers specified in "/etc/resolv.conf" or the Network -> Settings -> IP Settings -> DNS Server # will be used by your ClearOS box to do a DNS query for those hosts/IP addresses that it cannot resolve locally. See this wiki article to learn more about how recursive and caching DNS servers work.
| Code: |
C:\>NSLOOKUP 192.168.1.100/flexshare/gallery
Server: dns.tb.iss.as9143.net
Address: 212.54.40.25
*** dns.tb.iss.as9143.net can't find 192.168.1.100/flexshare/gallery: Non-existent domain
C:\>NSLOOKUP cpu.lan/flexshare/gallery
Server: dns.tb.iss.as9143.net
Address: 212.54.40.25
*** dns.tb.iss.as9143.net can't find cpu.lan/flexshare/gallery: Non-existent domain
C:\>NSLOOKUP cpu.poweredbyclear.com/flexshare/gallery
Server: dns.tb.iss.as9143.net
Address: 212.54.40.25
*** dns.tb.iss.as9143.net can't find cpu.poweredbyclear.com/flexshare/gallery: Non-existent domain
|
All of the above attempts to resolve above failed because you provided a Uniform Resource Locator (URL) to the DNS server. DNS servers do not translate URLs to IP addresses, or IP addresses to URLs. They translate IP addresses to Domain Names, or Domain Names to IP addresses. See this wiki article to learn more about URLs.
| Code: |
Thanks for responding.
Manually pointing the clients DNS to the COS box is not an option, because we have a lot of circulation of clients.
Port 53 UDP & TCP are both open on the standalone COS box.
AFAIK dnsmasq never runs on a standalone COS box.
|
Cool, having 53/UDP is right for the clients on your local LAN to use your ClearOS box as their DNS server. 53/TCP is only used when the DNS response packet exceeds 512 bytes, or when DNS zone transfers are made between DNS servers (which is not applicable in your case).
Hope this helps a bit. |
|
|
|
|
|
|
