Recommended Posts

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!!

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 ?

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

no, thats not the case.

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.

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....

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....

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.

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.

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.

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.

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.

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............

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.

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????

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

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

I think the answer of "You don't" is particular pertinent here.

As CPressland has stated, the fact that the Apache Web server (presumably running on a Windows box connected to the "domain" in question), the Domain's DC, and the clients actively looking to connect to the Apache Website will all be on the same domain, and connected accordingly, means you don't have to create a DNS record. As long as your Apache web server is called "website.met" you're all good!

Just make sure you are connected to the domain and as CPressland has stated, the DNS records will automatically be created on the DNS server

What is the name of the Apache server?

Start > Right Click Computer > Properties

PC1

all pcs here (except the dc) are named lik that with the number being the differece.

I think the answer of "You don't" is particular pertinent here.

As CPressland has stated, the fact that the Apache Web server (presumably running on a Windows box connected to the "domain" in question), the Domain's DC, and the clients actively looking to connect to the Apache Website will all be on the same domain, and connected accordingly, means you don't have to create a DNS record. As long as your Apache web server is called "website.met" you're all good!

Just make sure you are connected to the domain and as CPressland has stated, the DNS records will automatically be created on the DNS server

are you saying "it just works"? im sure id have to make a entry for this apache virutal hsot to be seeable by all....

"DNS records will automatically be created on the DNS server"

That is if the domain is not jacked up -- with a network admin that does not know how to create a A record, or where even to look for dns on the DC?

I am taking odds that prob not ;)

so you called your machine website.met ?? Really that is an odd name for a computer, could you post the output of hostname. And then just do a nslookup for the name that is output from hostname.

example

C:\Windows\System32>hostname

i5-w7

C:\Windows\System32>nslookup i5-w7

Server: pfsense.local.lan

Address: 192.168.1.253

Name: i5-w7.local.lan

Address: 192.168.1.100

C:\Windows\System32>

edit: Well if your computer is called PC1, then no its not just going to work.. You need to create the records in dns to point to the name you want for your website.

Do you have access to dns on the DC?

here

http://support.microsoft.com/kb/324260

How To Configure DNS Records for Your Web Site in Windows Server 2003

Same thing if 2k8 or 2k8r2, etc.. Send that link to your so called network admin

"DNS records will automatically be created on the DNS server"

That is if the domain is not jacked up -- with a network admin that does not know how to create a A record, or where even to look for dns on the DC?

I am taking odds that prob not ;)

so you called your machine website.met ?? Really that is an odd name for a computer, could you post the output of hostname. And then just do a nslookup for the name that is output from hostname.

example

C:\Windows\System32>hostname

i5-w7

C:\Windows\System32>nslookup i5-w7

Server: pfsense.local.lan

Address: 192.168.1.253

Name: i5-w7.local.lan

Address: 192.168.1.100

C:\Windows\System32>

edit: Well if your computer is called PC1, then no its not just going to work.. You need to create the records in dns to point to the name you want for your website.

Do you have access to dns on the DC?

here

http://support.microsoft.com/kb/324260

How To Configure DNS Records for Your Web Site in Windows Server 2003

Same thing if 2k8 or 2k8r2, etc.. Send that link to your so called network admin

no my machine is called PC1. the apache server has a virtual host called website.met the apache server is on PC1

here -- this is how you do it if you want to resolve website.met to your 192.168.1.99 address

post-14624-0-23822200-1337161780.jpg

See its a forward zone called met, with A record of website

I had to change what server I did my nslookup too, because I do not use that box as my dns

you could also do it with a cname pointing to your pc1.whaterdomainyourusing -- but lets just keep it REAL SIMPLE!!

Doesn't matter! Interface is the same, create a new primary forward zone called met, then A record of website.

Right click forward lookup zones, new zone, primary -- call it met

Then right click then new zone met and create A record website with your IP you want to point it too

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The quantum search for Time's origin had an equally mind-boggling conclusion by Sayan Sen Image by Steve Johnson via Pexels A theoretical study from researchers at the University of Surrey suggested that the direction of time may not be fundamentally fixed in certain quantum systems. The work, published in Scientific Reports, examined how the “arrow of time” could emerge from microscopic physics and found that time-reversal symmetry can remain intact even in models used to describe processes such as energy loss and thermalisation. The arrow of time refers to the observed one-way direction from past to future in everyday life. In macroscopic processes, this is easy to see. Spilled milk spreads across a table and does not gather back into a glass, and heat flows from hotter objects to colder ones. These processes shape the common sense idea that time moves in a single direction. However, at the level of fundamental physics, many equations do not prefer a direction of time. Time-reversal symmetry means that the same physical laws can describe a system whether time moves forward or backward. This has made it difficult to explain why irreversible behaviour appears in the large-scale world even when the underlying rules do not require it. Dr Andrea Rocco, Associate Professor in Physics and Mathematical Biology at the University of Surrey, described this contrast: "One way to explain this is when you look at a process like spilt milk spreading across a table, it's clear that time is moving forward. But if you were to play that in reverse, like a movie, you'd immediately know something was wrong – it would be hard to believe milk could just gather back into a glass. However, there are processes, such as the motion of a pendulum, that look just as believable in reverse. The puzzle is that, at the most fundamental level, the laws of physics resemble the pendulum; they do not account for irreversible processes. Our findings suggest that while our common experience tells us that time only moves one way, we are just unaware that the opposite direction would have been equally possible." The study focused on open quantum systems, which are quantum systems that interact with a surrounding environment. This environment, often described as a heat bath, can exchange energy and information with the system. The researchers used this framework to study how a direction of time might appear even when the underlying physics does not enforce one. A key part of the analysis involved the Markov approximation. This is a simplification used in many models where the system is assumed not to retain memory of its past states. The idea is that changes depend only on the current state, not on earlier history. This is commonly used when studying thermalisation, which is the process where a system settles into equilibrium with its environment. The study also used concepts such as master equations, including the Lindblad and Pauli equations, which describe how probabilities of different quantum states change over time. Another related model discussed was quantum Brownian motion, which describes the random-like movement of a quantum particle interacting continuously with its environment. In these descriptions, a “memory kernel” can appear, which is a mathematical term that accounts for how past states influence current behaviour. The researchers found that applying the Markov approximation did not break time-reversal symmetry. Even when the system interacted with an effectively infinite heat bath, the resulting equations of motion remained symmetric in time. This meant that the same mathematical description could, in principle, run forward or backward in time without contradiction. The study further showed that standard frameworks used in open quantum systems, including quantum Brownian motion and master equations like the Lindblad and Pauli forms, could be written in a time-symmetric way. These equations are typically used to describe processes that look irreversible, such as dissipation and thermalisation, but the results suggested they can also be interpreted as allowing evolution in both time directions. Thomas Guff, Research Fellow in Quantum Thermodynamics, said: "The surprising part of this project was that even after making the standard simplifying assumption to our equations describing open quantum systems, the equations still behaved the same way whether the system was moving forwards or backwards in time. When we carefully worked through the maths, we found that this behaviour had to be the case because a key part of the equation, the "memory kernel," is symmetrical in time. We also found a small but important detail which is usually overlooked – a time discontinuous factor emerged that kept the time-symmetry property intact. It’s unusual to see such a mathematical mechanism in a physics equation because it's not continuous, and it was very surprising to see it appear so naturally." The researchers also noted that deriving a one-way arrow of time from time-reversal symmetric microscopic dynamics remains an open problem across fields such as thermodynamics, statistical mechanics, particle physics, and cosmology. Their results suggested that some standard descriptions of irreversible behaviour in open quantum systems may be better understood using a time-symmetric formulation of Markovianity. According to the study, processes such as thermalisation, which are usually treated as irreversible, could in theory be described in a way that allows evolution in either time direction under the same rules. This does not imply that time reversal occurs in everyday life, but rather that the underlying equations do not strictly enforce a single direction. Overall, the findings suggested that the perceived direction of time may emerge from how physical systems are modelled and approximated, rather than from a fundamental asymmetry in the laws themselves. The researchers noted that this perspective could have implications for ongoing work in quantum mechanics, thermodynamics, and cosmology on the origin of time’s arrow. Source: University of Surrey, Nature This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing
    • A bit premature... 100% Marketing. Bizarre.
    • A $300 price hike is insane! No one is going to want to pay that much!
    • Since the 1st one flopped, there is really no reason to make another one. It's just losing money left and right.
  • Recent Achievements

    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      579
    2. 2
      +Edouard
      182
    3. 3
      PsYcHoKiLLa
      74
    4. 4
      Michael Scrip
      71
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!