31 replies to this topic

[metro2012]

i have a website setup internally using apache. its website.met. my ip is 192.168.1.99 in the domain controller i made a new A record point website.met to 192.168.1.99 i flushed the dns on the client and the client cannot resolve the website. y does it not work?

[+CPressland]

Well, the Web Server should be using it's full FQDN. So, if your domain was example.com then the Web Server should be something like webserver.example.com and you'd only need to setup a new a record for WebServer.

[still1]

metro2012, on 16 May 2012 - 07:18, said:

i have a website setup internally using apache. its website.met. my ip is 192.168.1.99 in the domain controller i made a new A record point website.met to 192.168.1.99 i flushed the dns on the client and the client cannot resolve the website. y does it not work?

one thing i can think of is the user's permission to the domain controller to resolve the dns!!

[+CPressland]

still1, on 16 May 2012 - 07:22, said:

one thing i can think of is the user's permission to the domain controller to resolve the dns!!

I'm fairly sure Windows Server's DNS doesn't require Authentication or IP-Whitelisting.

[metro2012]

CPressland, on 16 May 2012 - 07:22, said:

Well, the Web Server should be using it's full FQDN. So, if your domain was example.com then the Web Server should be something like webserver.example.com and you'd only need to setup a new a record for WebServer.

the domain is called mydomain.local so would i have to make a A record pointing at mydomain.local.website.met and then create a CNAME with that pointing to website.met ?

still1, on 16 May 2012 - 07:22, said:

one thing i can think of is the user's permission to the domain controller to resolve the dns!!

no, thats not the case.

[+CPressland]

No, you'd make an A record called website.met.mydomain.local.

Your Domain Name goes after the Hostname of the Device. If you want to be able to hit 'Website.met' directly with no further intervention then you need to create a new forward lookup zone called .met and add website* to it.

[metro2012]

CPressland, on 16 May 2012 - 07:37, said:

No, you'd make an A record called website.met.mydomain.local.

Your Domain Name goes after the Hostname of the Device. If you want to be able to hit 'Website.met' directly with no further intervention then you need to create a new forward lookup zone called .met and add website* to it.

i made a A record and it automatically put mydomain.local to its right but I removed it and left it website.met but I think it made its own foward lookup zone..........

obviously i made a mistake but sadly im not the network admin so i cant be saying lets try this and that....

[+CPressland]

Well, your Network admin WILL know what he needs to do to setup something like this. Just make sure the hostname on your Linux box thats running the WebServer is setup correctly and has a Static IP.

[metro2012]

CPressland, on 16 May 2012 - 07:46, said:

Well, your Network admin WILL know what he needs to do to setup something like this.

he doesnt. i just told him that i wanted to point website.met to my ip because i am running a web site with apache there and he told me that i would have to tell him how to do it as he does not know how to.

told him 2day and here it is....

CPressland, on 16 May 2012 - 07:46, said:

Just make sure the hostname on your Linux box thats running the WebServer is setup correctly and has a Static IP.

it is a windows box and yes: it is static.

[+CPressland]

metro2012, on 16 May 2012 - 07:49, said:

he doesnt. i just told him that i wanted to point website.met to my ip because i am running a web site with apache there and he told me that i would have to tell him how to do it as he does not know how to.

Then he shouldn't be a working in Networking - my partners 9 year old can already handle DNS configuration.

metro2012, on 16 May 2012 - 07:49, said:

it is a windows box and yes: it is static.

If it's Windows, Bind to the Domain and it's instantly resolvable. Active Directory will automatically add the appropriate A Records.

[metro2012]

CPressland, on 16 May 2012 - 08:09, said:

Then he shouldn't be a working in Networking - my partners 9 year old can already handle DNS configuration.

go tell him (my boss) that........he didnt even know where to go in windows server to do it.

CPressland, on 16 May 2012 - 08:09, said:

If it's Windows, Bind to the Domain and it's instantly resolvable. Active Directory will automatically add the appropriate A Records.

so therefore, I create a new A record and just leave the mydomian.local that is automatically appended to the right. ill try asking him to do tha if it doesnt work, then i guess ill just leave it alone.

[+CPressland]

You don't need to create anything, if the Windows Server that is running the Apache Server is joined to the domain as website.met then it'll automatically be resolvable.

[metro2012]

CPressland, on 16 May 2012 - 08:17, said:

You don't need to create anything, if the Windows Server that is running the Apache Server is joined to the domain as website.met then it'll automatically be resolvable.

?

i have apache server on pc 1 (my pc) dc is another pc, pc 2, i want the apache server to accessed by pc 3, 4, 5 (other pcs) on dc. all connected to dc.

it is not on ws/dc............

[+CPressland]

Okay

Domain name is mydomain.local
Domain Controller for example is called dc.mydomain.local
Apache Server is called website.met.mydomain.local
Other PCs are called PC1.mydomain.local, PC2.mydomain.local, PC3.mydomian.local etc

When website.met is joined to mydomain.local it gets the FQDN of website.met.mydomain.local

When a user types http://website.met into a Web Browser it'll search the network for a name containing website.met and then try the outside world. This is called a Search Domain, when it finds website.met.mydomain.local it'll automatically connect to the correct IP address and load the page.

[metro2012]

CPressland, on 16 May 2012 - 08:25, said:

Okay

Domain name is mydomain.local
Domain Controller for example is called dc.mydomain.local
Apache Server is called website.met.mydomain.local
Other PCs are called PC1.mydomain.local, PC2.mydomain.local, PC3.mydomian.local etc

When website.met is joined to mydomain.local it gets the FQDN of website.met.mydomain.local

When a user types http://website.met into a Web Browser it'll search the network for a name containing website.met and then try the outside world. This is called a Search Domain, when it finds website.met.mydomain.local it'll automatically connect to the correct IP address and load the page.

yes. exactly. the first five lines describe exactly the situation.

so how would i set that up on the dns server????